Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow collection admins to define the list of ranks relevant for their collection #353

Open
m-r-c opened this issue May 25, 2016 · 2 comments
Labels
Project - IEK Garragal project

Comments

@m-r-c
Copy link
Contributor

m-r-c commented May 25, 2016

When creating a new profile, the editor can manually construct the hierarchy if the name they entered is not matched. However, the hierarchy requires a rank for each level, and the list of available ranks is currently hard-coded.

The collection admin should be able to create a list of ranks that is relevant for their collection.

@m-r-c m-r-c added the IEK label May 25, 2016
@RobinaSanderson
Copy link

From an eFlora perspective, the capability to manually construct the hierarchy within a collection will be handled by the NSL alternate tree functionality.

@RobinaSanderson
Copy link

If this issue is solved then #494 is no longer required.

@pbrenton pbrenton added Project - IEK Garragal project and removed IEK labels Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Project - IEK Garragal project
Projects
None yet
Development

No branches or pull requests

3 participants