Topic/Who | Tickets | Notes | Decision |
|---|
Introductions Code of conduct Dev Pri meeting structure Advice on approaching tickets How to prepare for upcoming meetings What should you to do after meetings Questions
| | https://archivesspace.atlassian.net/wiki/x/HoBLAg | |
| https://archivesspace.atlassian.net/browse/ANW-1095 https://archivesspace.atlassian.net/browse/ANW-1029
|
|
|
Maggie Hughes | https://archivesspace.atlassian.net/browse/ANW-281 https://archivesspace.atlassian.net/browse/ANW-336
|
|
|
Randy Kuehn | https://archivesspace.atlassian.net/browse/ANW-947 https://archivesspace.atlassian.net/browse/ANW-1017
| It looks like this CSV export/import might be a good plugin candidate
Recommend: Perhaps we could push the location import/update/export to Community Development I think a reset default preferences option would be a useful UI upgrade
Recommend: If Usability doesn't need to weigh in, either push to Development or Community Development
| Passed for community developer as plugin. Passed for community developer to add to each level of preferences.
|
Daniel Michelson | https://archivesspace.atlassian.net/browse/ANW-956 https://archivesspace.atlassian.net/browse/ANW-121
| The submitter is correct that it is inconsistent for the PUI to omit date labels for creation dates. I do not see any downside to this proposal and recommend moving it forward for implementation I agree that this is a desirable feature and incorporating it into the global/repository/user preferences system would be logical from the user perspective (as suggested in the broader SIEWG recommendations referred to in the comments). Aside from the Finding Aid Data section of resource records, the ticket does not specify which parts of which records or sub-records should be able to be hidden. That would need to be determined before moving the ticket forward.
| Push to development Dev Pri will be investigating the possibility this type of feature
|