2018-12-18 Meeting notes

Date

Dec 18, 2018 2pm EST

Call-in

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

Attendees

Round robin of Jira assignments

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 items

Who

Item

Notes

Decision

Who

Item

Notes

Decision

Announcements?

Fast Track

ANW-777: Capitalize "Creator" as the default <origination> LABEL value.Closed-Complete

simple PUI label: PASS

pass

Fast Track

https://archivesspace.atlassian.net/browse/ANW-604

simple PUI label: PASS

pass

Fast Track

ANW-603: In resource records, the Value displays on the PUI for the Finding Aid Status field, instead of the TranslationClosed-Complete

simple PUI label: PASS

pass


Edgar

ANW-751: EAD export problem with escaping mixed contentClosed-Will Not Do

Rec: Unable to further test but this should pass. It seems like description has a solution to the issue that might catch all/most fields.


pass

Edgar

ANW-474: As an archivist, I would like exports to be handled as "jobs" in order to allow for large exports to not cause timeout issues.Closed-Will Not Do

Rec: There isn’t a bulk export of XML within core as far as I can see. We have a 20MB EAD when exported and have been able to export many times, but had issue prior to v2.1. That said, this could be an issue in the future for large records. I would recommend passing if we could add a separate background job export option along with the regular export for trouble records. Otherwise, this issue was technically completed when it was done for PDF.

Awaiting More Information

Edgar

ANW-783: Subject record linking is not precise enoughClosed-Complete

Rec: Pass using Mark Cooper’s notes about linking using database associations instead of the search functionality.

Pass

Julia

Limit RDE: ANW-522

 

 

Julia

Archival Objects advancing bug ANW-736

 

 

Julia

Physical Storage info in Resource tree? ANW-301

 

 

Maggie

[from earlier] Boolean technicality https://archivesspace.atlassian.net/browse/ANW-171

Rec: Unable to confirm myself, but pass with Laney’s notes

Awaiting more info

Maggie

[from earlier] See all records created by particular user: ANW-744

Rec: Pass

Awaiting more info

Maggie

ANW-800: LCNAF import plugin should match to existing lcsh subject source valueClosed-Complete

Can confirm that this is still an issue. User guide doesn’t include info on importing subjects via LCNAF plugin. Add this to ticket?

Rec: Pass

pass; emailed Kevin Clair re user guide and importing subjects

Laney/Lora

ANW-437: When migrating from AT to ArchivesSpace, external links in accession and resource records to files on a network server no longer work due to the insertion of "file://". This needs to be fixedClosed-Will Not Do

Rec: Close Won’t do

Close

Laney/Lora

https://archivesspace.atlassian.net/browse/ANW-757

 

pass to stop automatically mapping to the optional caption field

Terra

Events: ANW-358

Still awaiting more info? I’m not really sure what the issue is/what user is asking for…

Awaiting more info - seeking more community input on whether this is a wider issue/priority

Terra

Events 2: ANW-509

Tried to recreate issue, but am not able to create a new event. Getting an error: Event Date/Time - must specify either a date or a timestamp UTC Timestamp - must specify either a date or a timestamp.

Rec: pass (if issue still exists)

wide spread errors within events

Awaiting More Info - Christine will explore

Terra

ANW-688: adding two extents to a Resource record causes some Notes to repeat- V. 2.2.1Closed-Will Not Do

Recreated in sandbox and don’t see any Notes repeating in newest version.

Rec: close?

Close

Alicia

ANW-520: As a processing archivist, I would like RDE(s) to be capable of editing a selected set of componentsClosed-Will Not Do

 

close - duplicate in favor of ANW-561

Alicia

https://archivesspace.atlassian.net/browse/ANW-153

Could not replicate in 2.4.1

close

Alicia

ANW-408: Review and revise accession importClosed-Will Not Do

 

Awaiting More Information

Lydia

ANW-372: As a processing archivist, I would like the RDE option to support linking up to three agents and three subjectsClosed-Will Not Do

Added specs, which are also in SIEWG recs. Question is whether Subjects and Agents should be linked to Archival Components, not just collection-level record? It makes sense for Digital Objects, but I am unsure about Series, Files, and Items, etc. Awaiting more info/community input.

Awaiting More Information

Lydia

ANW-378: Documentation could use an advanced query mini-cookbookClosed-Will Not Do

This ticket is really old and doesn’t have any specs. There is not enough info to move it forward. Notified both Dallas and Kevin for Technical and User Documentation. Rec: Close

Closed

Lydia

https://archivesspace.atlassian.net/browse/ANW-471

This ticket is old and I haven’t been able to get an answer about what it is actually suggesting. I recommend closing this ticket since the respondents haven’t replied since April, which doesn’t demonstrate a lot of interest in the ticket issue.

Closed

Lydia

https://archivesspace.atlassian.net/browse/ANW-522

Having a hard limit of RDE of 50 lines (as Mark suggested) sounds like a good idea to me, especially since there isn’t a confirmation click-through whenever the window is closed. (That confirmation window is much needed!) Rec: pass

close - Lydia will comment about why

 

see https://archivesspace.atlassian.net/browse/ANW-391 for RDE confirmation issue

Patrick

https://archivesspace.atlassian.net/browse/ANW-299

Unable to replicate and original reporter is no longer able to replicate. Rec: close

close

Patrick

https://archivesspace.atlassian.net/browse/ANW-556

Not an error. Two fields are different.

Agreed with Mark Custer's interpretation of this. Location barcodes are for identifying physical location units, whereas the containers are for individual containers like a box.

Rec: Some better control of Location barcodes could be helpful though. Either through suppression or forced uniqueness.

close

Patrick

https://archivesspace.atlassian.net/browse/ANW-275

Dave Mayo has explained the situation well and a solution. Can confirm and replicate the behavior.

Rec: pass

Pass

William

[Lydia: Is this already done?]https://archivesspace.atlassian.net/browse/ANW-341

 

 

William

https://archivesspace.atlassian.net/browse/ANW-312

 

 

William

https://archivesspace.atlassian.net/browse/ANW-453

 

 

Action items

Decisions

  1. Next meeting January 29th (the last Tuesday of each month) 1-2:30pm EST. Thank you for your flexibility in scheduling!