Request - how-to for bulk edit containers

[fenuccio]

Help us understand your request (check below):

• search or data request (help with SQL or provide the specific fields you are trying to retrieve for your collection)
• add a new Github user to the Arctos Users team
• a new barcode series
• a new term for data entry or management
• a change or new report or label
• update to an Agent (split, merge, or other type of change)
• bulkload changes (to Agents, Identifiers, etc that are not already available as a bulkloading tool)
• new feature or otherwise a good idea to make Arctos even better
• quarantine taxon name and suggested replacement (please supply links)
• other

Describe what you're trying to do

@happiah-madson realized that in order to bulk edit containers, users need to not only have manage_container, but also manage_record in order for this to work. This should be better documented.

[happiah-madson]

@mkoo can we put this in https://arctos.database.museum/Admin/user_roles.cfm somewhere?

[dustymc]

What could be considered "better documented"?

• there's a clearly-marked thing of importance to read
• there's a dedicated and clearly-documented role

I think we're all happy to make things better, but I don't know what that might mean.

put this in https://arctos.database.museum/Admin/user_roles.cfm somewhere?

Heavy NO from me - we struggle to maintain our normalized documentation, if my job comes to involve updating dozens or hundreds of forms when something changes then - well, I just can't, there's no possible way I'd have time to do that alongside even my most basic 'keep Arctos alive' tasks.

Component loaders (like everything else) can carry page documentation, that is much easier to maintain, possibly that's a better pathway (but see above, not sure I'm understanding the problem so. ???).

[happiah-madson]

well, I just can't, there's no possible way I'd have time to do that alongside even my most basic 'keep Arctos alive' tasks.

Totally understood. Let me think about this a bit more.

[happiah-madson]

Component loaders (like everything else) can carry page documentation, that is much easier to maintain, possibly that's a better pathway (but see above, not sure I'm understanding the problem so. ???).

By page documentation do you mean: https://arctos.database.museum/loaders/bulkEditContainer.cfm ? Is this the place where it is the easiest to maintain documentation? When I was trying to give access to a person, I looked at all documentation listed to read for the tool on https://arctos.database.museum/Admin/user_roles.cfm based on what permissions the tools directory said I needed. I totally did not realize that this information was on the component loaders and it's much more extensive than what is on tools directory. So that's on me. I'll just know to look here in the future.

[dustymc]

page documentation do you mean

[happiah-madson]

@dustymc and @mkoo

I want to just outline workflow to see if there is a way that we can make this more intuitive. So....

I have a student who needs to be able to bulk edit containers (for instance, they need to be able to convert a series of labels into cryovials or they need to add labels to existing containers). I go to Tools Directory, Manage Operators, and then click on the user roles page (https://arctos.database.museum/Admin/user_roles.cfm) to determine which roles are required and make sure the user has read all required documentation for those roles.

However, in the Roles section, the row for manage containers (https://arctos.database.museum/Admin/user_roles.cfm#manage_container) says: Create, delete and edit containers. Prerequisite: view_container. It does not include that you also need manage_records to use the bulk edit tool and component loaders. The packages section at the top does not include information about this kind of use case. So, there is no clear path to figuring out what you did wrong when you assigned view_container and the user still does not have access.

Would it be possible to move the "packages" table to the Arctos User Handbook to allow more community members to easily edit and add different types of users to the options without requiring DBA assistance. We could reciprocally link from that handbook page to the user roles page (https://arctos.database.museum/Admin/user_roles.cfm) so that there is no need to update documentation in more than 1 location. We could also potentially link to this page from component loader pages, such as: Container: Bulk Edit (https://arctos.database.museum/loaders/bulkEditContainer.cfm).

Even more helpful would be adding that the prerequisites for manage_container are "view_container if doing single container edits" and "view_container and manage_record if doing bulk container edits" in the Roles description on the user roles page (https://arctos.database.museum/Admin/user_roles.cfm).

@campmlc @falco-rk