Item | Who | Notes | Decision | |
---|
Announcements? | | | | |
Old business
| Lydia
| 1. ANW-664
2. ANW-691 3. ANW-214 4. ANW-538 5. ANW-349 possibly, but I don’t know if a community developer would know how to do this a nice usability feature priority is low and could be trivial instead
6. ANW-97 7. ANW-553 8. ANW-348 no - sounds complex a nice usability feature priority minor ok
9. ANW-559 10. ANW-564 11. ANW-738 12. ANW-759 13. ANW-808 14. ANW-799 15. ANW-806 16. ANW-809 17. ANW-816 18. ANW-843 no? not sure how complex it would be to fix priority major, not sure it should be minor, but it would be a helpful function
19. ANW-908 |
| |
| Maggie | ANW-616 no?, complicated and tied into SIEWG work
ANW-215 yes
ANW-453 yes, seems like enough info inticket – split on periods or dashes, cram anything remaining into final id field
ANW-468 no, it’s already assigned
ANW-332 no?, might involve search
ANW-340 no? how tricky is sorting?
| | |
| Alicia | ANW-255 y/n to community developer? priority/other comments?
ANW-256 y/n to community developer? priority/other comments?
| | |
| Edgar | ANW-277 No to community developer? It would require a reliable way to detect an index is happening on multiple environments and thus some architecting is required by the core team.
ANW-273 Yes to community developer. If these are direct edits but probably not if this requires programming to pull curated definitions on the fly.
| | |
| Terra | ANW-615 y/n to community developer? priority/other comments?
ANW-601 y/n to community developer? priority/other comments?no? did not received further info from original submitter.
ANW-601 yes--Christine investigated issue.
ANW-638 y/n to community developer? priority/other comments?
yes
ANW-658 y/n to community developer? priority/other commentsyes? is this already being worked on?
| | |
Jiras | | | | |
| Alicia | https://archivesspace.atlassian.net/browse/ANW-838 https://archivesspace.atlassian.net/browse/ANW-357 https://archivesspace.atlassian.net/browse/ANW-700
| 1. 2. 3. | |
| Edgar | ANW-811 As this does not seem to affect anyone, I am unsure if this should remain an issue. I imagine there could be some sort of “refactor” event to deal with code cleanup eventually. I could not install a fresh application to try and repeat this issue.
ANW-499 I am unable to determine what exactly this issue is about, due to the title and description. Apologies.
ANW-921 If the citations are supposed to be DACS compliant, then this issue is relevant and should be worked on as citations contain the url and accessed date.
| 1. 2. 3. | |
| Terra | https://archivesspace.atlassian.net/browse/ANW-810 https://archivesspace.atlassian.net/browse/ANW-548
| 1. 2. | |
| Maggie | https://archivesspace.atlassian.net/browse/ANW-440 https://archivesspace.atlassian.net/browse/ANW-859
| Not sure this quite as much as much info as it needs, but it’s closer than last time. Question of how to import the call numbers (which id field they map to) relates a bit to ANW-453 – might want to link to it. Rec: pass?
2. See Christine’s comment re ANW-698. Since ANW-698 is in awaiting more info, recommend passing 859 and leaving a comment that it is dependant on 698 and linking to that ticket. | 1. 2. |
| Lora/Laney | https://archivesspace.atlassian.net/browse/ANW-737 https://archivesspace.atlassian.net/browse/ANW-901
| 1. 2. | |
| Lydia | https://archivesspace.atlassian.net/browse/ANW-789 https://archivesspace.atlassian.net/browse/ANW-919
| 1. 2. | |