Lydia planning to create a summarizing blog post for ArchivesSpace in January/February
Ticket tags
“Metadata” tag (Link to board) conflates tickets that deal with metadata with tickets where we want MS sub-team to weigh in. Could we create a new tag for the sub-team?
Does Usability have a similar situation?
Another idea is to add another column to the Kanban boards for “For Subteam Review” where someone from Dev. Pri. comments on the ticket which subteam needs to view it, and once the ticket is ready for Dev. Pri. again, the subteam person comments on the ticket and the original Dev. Pri. person adds it to the next agenda.
Tickets
Ticket theme for today’s meeting: Mostly bug tickets, with “older” Awaiting More Info feature request tickets
Confirmed in v2.7.0. No scroll bar and cannot key down the list either. Could not scroll or key down via the container record either. (Browse view is workaround.) Rec: pass.
Helpful hints aren’t appearing in v2.7.0. Still only appears hint if an additional assessment attribute has already been created. Rec: pass.
New options added. Choose and pass? Or I can do a flash survey on listserv, update ticket with winning option, and pass it.
My personal opinion is that this should pass. A useful feature that has been painstakingly spec’d out by Cory
Usability looked at this ticket and felt that, even though it would be nice to have a feature to display digital objects on the resource view, this is too Repository-specific and should either be a plug in or more flexible configurable option
Usability looked at this and felt it was useful for both staff and PUI, to maximize the ability of dynamically generated finding aids.
Usability felt this was a useful feature. I forget if we discussed this and said the programming architecture is too complex to fix?
This is a new “bug” that would be nice to fix soon. Endorsed by Usability