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?
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.