-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature Request - Add remarks to table collector #119
Comments
This would be soooo helpful for so many reasons. And as you can see from the multiple links above, has been discussed for a long time. |
Something like this would be really great. |
This sounds like a great idea that would solve multiple issues. Feasible? |
Agreed, this would be incredibly helpful! |
Cultural Collections WG prefers this a a priority action if considering against issues https://github.com/ArctosDB/code-table-work/issues/36 and https://github.com/ArctosDB/code-table-work/issues/37. |
AWG Issues discussed, general consensus is to proceed. Considerations:
|
Cultural collections WG reviewing proposed definition change of ctcollector_role - Creator in order to move request forward. |
Be sure to look at the discussion https://github.com/orgs/ArctosDB/discussions/5404 |
I think this is all resolved and ready for dev?? |
Anything you need from cultural collections WG? |
Is your feature request related to a problem? Please describe.
Further specificity is needed on agent roles; see ArctosDB/arctos#2579.
Describe what you're trying to accomplish
By creating an Agent Remarks field we'll be able to clearly distinguish these very specific types of activities by two separate artists, for example (see ArctosDB/arctos#2579).
Describe the solution you'd like
Add a remarks field next to the individual agent names that appear in the Agents section on a catalog record. This could appear in a table like the verbatim agents do.
Describe alternatives you've considered
Creating a bunch of different highly specific agent roles (see ArctosDB/arctos#2579)
Additional context
Here's an example screenshot of how this would resolve this comment:
The text was updated successfully, but these errors were encountered: