Date
12 ET/ 11 CT/10 MT/9 PT
Call-info
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/619789499
Or iPhone one-tap: US: +16468769923 (619789499#) or +16699006833 (619789499#)
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 6468769923 or +1 6699006833 or +1 4086380968
Meeting ID: 619 789 499
International numbers available: https://zoom.us/zoomconference?m=lfJNhr4XU-I8p7oRrXXwebNlh57Ti7kq
Participants
Goals
Prioritize new and awaiting more info tickets related to results of the Dev Pri survey:
Configurability of the public interface (38.85%)
Custom Reports (37.41%)
Rapid Data Entry (34.53%)
Importing CSV for Resources (such as the Harvard plug in) (33.81%)
Searching the public interface (33.09%)
Configurability of the staff interface (31.65%)
Visual Layout of the public interface (28.06%)
Built-in Reports (27.34%)
PDF generation for records in the staff or public interface (26.62%)
Reconceptualizing the Digital Objects module (25.18%)
Links
Kanban boards:
New bug reports: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15
New feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16
Link to ArchivesSpace sandbox: http://test.archivesspace.org/
Discussion topics
Who/What | Tickets | Notes | Decision |
---|---|---|---|
Roll call/ Announcements | |||
From Usability |
2. No movement on this ticket since 2017. Was looked at by reports subteam but no action. 3. This ticket has been an action item on several DevPri meetings- ‘will be referred to TAC as a possible use case for a notification system’. From my experience there is demand for such a feature. (Also addressed in this ticket: https://archivesspace.atlassian.net/browse/ANW-923 .) 4. Facets of this can be drawn out with existing reports (such as Shelflist Report and Resources & Instances), though it would be more useful to be able to export a CSV directly from the collection results, rather than across all collections. Usability would like this to pass. *Note: Available ‘Download CSV’ options draw across all records of a certain type (Location, Container Profile, etc.) without specificity, so I wonder how feasible a selective Top Container CSV download could be. 5. Usability would like this to pass with this internal note. Is there currently a way to create a custom repository field? 6. Addressed and reporter recommends closing. | ||
| |||
| |||
2. Making citation information compatible with citation software certainly seems like a useful addition and I recommend moving to ready for implementation, provided there is enough information in the ticket for the developer. 3.
| |||
| |||
1.) Last comment on this ticket was from Lora in 2018 indicating that it is still an issue for “basic” users and should be addressed. I was not able to replicate on my machine because it’s a Mac and according to ticket is a PC problem. It doesn’t seem like anything has changed here so I recommend passing the ticket. Could be ok for a community developer, though pinpointing exactly what’s happening may be tricky since the circumstances are so specific. 2.) The last activity on this ticket was in 2016, requesting detailed information on how the feature should work. This info was not provided. Could either keep it as awaiting more info, since that is true, or close it since there doesn’t seem to be much continuing interest. 3.) Given that the ticket is over 3 years old, seems specific to a workflow that may not be shared by | |||
2. This ticket has a lot of viewers (5). Selfishly, I would like this ticket to pass. I don’t think the community really engages in the Jira system, so we haven’t received any interaction on this ticket, besides these watchers, but I do think that this is getting at a desire to be able to compile records created or updated by a certain person. I’m not sure how it would work if a record is updated by someone else (if it would also stop showing up as “stats” for the earlier person, for example). 3. Selfishly, I would like this to pass, but I don’t know how this would work with multiple languages. 4. This ticket was brought up on the member list on 5/21 by people from U T Austin, Smithsonian, BYU, and Purdue U. They described “Purdue is in the same situation with slowing classifications workflows. After initiating a project earlier this year to attach a classification to each accession or resource record we have also seen a noted increase in load times when attempting to attach a classification to an accession or resource record on the staff side interface. We had an identical experience in 2.6.0 and recently upgraded to 2.7.1, where the issue persists. As others shared, the load time appears to be directly related to the number of records attached to classifications. […] This is an increasing work impairment for our unit.“ I’m not sure whether there needs to be actual specification on how to improve the load time, but it is a big problem! |