Item | Presenter | Tickets | Notes | Decision |
|---|
Roll call and announcements |
|
| | |
Review of initial survey results | | Around 120 responses. Strongest responses for: Lydia planning to create a summarizing blog post for ArchivesSpace in January/February | Smith had a meeting to talk about the priortization survey and had some questions. Some of the choices/prompts seemed vague while others seemed specific. Not much explanation of definitions. Unclear how developers work and priorities get determined. Q: Will this survy have an influence over what the Program team/Developers work on? A: Not necessarily. The Dev Roadmap. Christine goes through the tickets passed by Dev Pri and picks quarterly themes based on those tickets. Tickets then grouped and then the Dev team works through them. After survey closes, we will share results with the whole Dev Pri sub-team.
| |
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. | Consensus that a new column “For Sub-team Review” would work well. Do we also need another status for “Waiting for specification”? Do we need a definition of the statuses? Does Community Dev include plug-ins? Laney McGlohon (Unlicensed) will bring this to Christine Di Bella and talk about documenting the statuses and go from there. | |
Tickets | | Ticket theme for today’s meeting: Mostly bug tickets, with “older” Awaiting More Info feature request tickets | | |
| Alicia Detelich | https://archivesspace.atlassian.net/browse/ANW-461 https://archivesspace.atlassian.net/browse/ANW-926 https://archivesspace.atlassian.net/browse/ANW-803
| | |
| Lori Dedeyan (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-833 https://archivesspace.atlassian.net/browse/ANW-873 https://archivesspace.atlassian.net/browse/ANW-869
| This seems like a browser issue specific to reporter. Is not an issue in sandbox PUI. This only affects text sub-notes in multi-part notes. Recommend moving forward with development. Have not been able to replicate this issue in 2.7.0.
| Daniel Michelson will ask colleague to add info to ticket (trying to pull width of right hand side nav bar). Move to Awaiting More Info. Pass. Lori Dedeyan (Unlicensed) leave comment to ask them to upgrade to v2.7 and let us know if issue is resolved. Move to Awaiting More Info. Look at this ticket again next time.
|
| Randy Kuehn | https://archivesspace.atlassian.net/browse/ANW-926 https://archivesspace.atlassian.net/browse/ANW-168 https://archivesspace.atlassian.net/browse/ANW-350
| Digital objects remain in EAD export if they're deleted before being removed from component.
Multiple digital objects remained when tested in v2.7.0 Confirmed...multiple repositories are not simultaneously accessible within browser - v2.7.0 Related to ANW-349 which is awaiting more info...need spec
| Pass. Randy Kuehn leave comment that this is unnecessary and out of scope for now. Close. Randy Kuehn leave comment asking Usability to review. Move to sub-team review.
|
| Daniel Michelson | https://archivesspace.atlassian.net/browse/ANW-873 https://archivesspace.atlassian.net/browse/ANW-820 https://archivesspace.atlassian.net/browse/ANW-355
| Could not reproduce Clear error, have asked for clarification about proposed solution. The technical details of this are a little over my head, but it is a well described proposal for a useful new feature. Recommend approving.
| Already done. Daniel Michelson will follow up with commenter. Pass. Pass.
|
| Maggie Hughes | https://archivesspace.atlassian.net/browse/ANW-897 https://archivesspace.atlassian.net/browse/ANW-257 https://archivesspace.atlassian.net/browse/ANW-214
| 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.
| Maggie Hughes will comment that issue happens in Resources, too. Pass. Pass. Maggie Hughes leave comment that screen reader needs to understand what is indicated visually/alternative text “Unpublished”; the accessibility of the options should be tested; circle back with Usability if needed. Pass.
|
| Edgar Garcia (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-833 https://archivesspace.atlassian.net/browse/ANW-717 https://archivesspace.atlassian.net/browse/ANW-76
| Could not repeat issue on Firefox or Chrome. Devs will not be able to fix if they cannot replicate. Isn’t an issue anymore. This appears to be completed.
| skip! done! Close - done close - done!
|
| Lydia Tang (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-357 https://archivesspace.atlassian.net/browse/ANW-810 https://archivesspace.atlassian.net/browse/ANW-477 https://archivesspace.atlassian.net/browse/ANW-682 https://archivesspace.atlassian.net/browse/ANW-953 https://archivesspace.atlassian.net/browse/ANW-919 https://archivesspace.atlassian.net/browse/ANW-769
| 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 Also endorsed by Usability Also endorsed by Usability
| Laney McGlohon (Unlicensed) will leave comment and talk to Christine Di Bella about sending this out for community comment. Lydia Tang (Unlicensed) will leave to explore as a plug-in or configurable. Move to Community Dev.
|
| Lora Woodford , Laney McGlohon (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-141 https://archivesspace.atlassian.net/browse/ANW-605
| | I believe this is already done so closed the issue as completed. I believe this is already done so closed the issue as completed.
|