We’d rejected a similar request in a previous ticket, but this one has much clearer reasoning. Keep open.
I don’t see anything in this ticket that requires review by the Metadata Standards team. It’s a straightforward request for a new feature. Since it’s in reference to a plugin, recommend assigning to community developer.
Same as previous, except that I’m not sure there’s enough information for sending to community developer. Change to either ready for community developer or awaiting more information.
Same as 3
Same as 3
Not sure about this ticket, there’s no real information in it. What would we be asking Metadata Standards to weigh in on?
This should be sent to Metadata Standards to determine whether VRA Core export for digital objects is an appropriate goal (I suspect the answer is no, but I’m not familiar with VRA).
Unanimously positive responses about this ticket after sharing it on the list. However, it would be a lot of work. Maybe put it on the community developer list?
Usability looked at this and thinks it looks good with Ed’s final comments. Pass?
No activity since 2016- last comment suggests issue may be resolved. Close?
2. This hasn’t been updated in several years, though issue may still be relevant. Needs more information.
3. Request is clarified in comments, but the ticket has not been updated since 2015. Close?
4. This seems to fit into the larger set of recommendations regarding the user interface. Recommend closing this specific ticket.
5. Further info/mapping was supplied by Cory Nimer a couple of months ago, in response to DevPri request- pass on?
6. Have not been able to replicate issue but would be curious if others have had it- agree with 2018 DevPri recommendation to solicit input from users.
7. While not as immediate as having location information directly within a resource/ accession, the top container management functionality does do what this request is asking (show all locations associated with a resource/accession). Recommend closing.
8. This ticket and associated tickets have not been worked on for several years. Close?
Still relevant, several review and revise tickets exist that should be done. Keep as is. Give to Metadata Standards?
Usability team wants this feature. More info is still needed due to infinite scroll issue.
Usability closed this ticket. So keep closed.
Recommend closing this. Not only is is from 2014 but Dev. Pri. already agreed once that the current default behavior is wanted. A plugin could resolve a particular Institution’s custom desires. Close this.
I have had issues with adding users while having ldap active. You blindly have to add the user with a random password. I would like for this issue to be passed.
This is still relevant and would work well with ANW-523 so maybe link both of them. Both would require assistance from an institution with ldap.
This seems a duplicate of ANW-523 so we might want to merge them and close one. Again, the idea is sound and should be passed once there is enough info.
Tested in v2.7.0 and is no longer an issue. Rec: close.
Confirmed that EAD tags for bold text are still not working in PUI. Not sure what the preferred tag is/does it matter – the ticket uses span. <span> is html, <emph> and <title> are EAD. Doesn’t display in PUI:<span class="bold emph">, <emph render="bold">, or just <emph>. <title render="italic">does work, but changing the attribute value to “bold” doesn’t change it. Rec: pass.
Comfirmed issue in v2.7.0. Also noticed in MARCXML export that some relator terms export as translated and some as code. Rec: pass.