2020-01-29 Meeting notes

Roll call and announcements

Discussion items

1. How should the survey results inform Dev Pri’s work?

2. Should we be looking at formalizing ways to allow institutions to petition their plug-ins to become core code? How can/should we do this?

3. Note new (draft) documentation for Dev. Pri. Leader Guidance (aka, Lydia’s brain download). Please feel free to read, discuss, comment, and edit!

4. Process for bug fixes submitted by Metadata Standards team (example)

1. It would be good to focus on issues that relate to the top choices of the survey results.

2. Process for evaluating potential feature contributions and turning a plugin into core code. These documents informs on what to do or how to go about adding a plugin formally into core code.

3. Lydia brain download Leader Guidance

4.  

Next month’s agenda

@Edgar Garcia (Unlicensed)

Big ticket sweep idea.

Tickets

@Randy Kuehn

1. https://archivesspace.atlassian.net/browse/ANW-936

2. https://archivesspace.atlassian.net/browse/ANW-903

3. https://archivesspace.atlassian.net/browse/ANW-243

1. Confirmed typeahead does not accommodate hyphenated entries (v2.7.0)
   Recommend: pass (replace common typeahead scenario punctuation with spaces)

2. Confirmed controlaccess title tags are skipped during EAD import (v2.7.0)
   Confirmed controlaccess title is included as subject object during EAD export (v2.5.x)
   Recommend: pass (include uniform title tags as subject objects durning EAD import)

3. Confirmed EAD import adds non-standard values to enumeration field Date Type (v2.7.0)
   Christine reached out to Laney McGlohon for additional information (2017)
   Attempted to identify solution by examining sourcecode...data validation could be possible solution...inability to add/modify/delete new date types (enumerations) through AS interface can be problematic
   Recommend: more information needed to unveil depth of problem and solutions

1. Pass

2. Pass

3. Add a comment to the ticket that specifies passing this contingent on adding any enumeration fields that are uneditable through the interface or API should fail with an error message that is helpful and informational.

@Edgar Garcia (Unlicensed)

1. We’ve had this issue, our workaround is to manually edit the record and save it so it is reindexed into existence.
   Recommend: pass

2. I could not find documentation about endpoint permissions required to confirm if the search endpoind indeed only requires view_all_records but this should probably be looked at.
   Recommend: pass?

3. Is there enough information for the devs to take this ticket over?
   Recommend: pass contingent on Dev response.

1. Pass

2. Pass but also contact the tech docs and API task force to review API permissions and authentication per endpoint. @Edgar Garcia (Unlicensed) to add a comment.

[LT update: status changed, pending Edgar’s comment]

3. Move to Waiting for More Information and ask the community if there is interest.

@Maggie Hughes

@Lydia Tang (Unlicensed)

3.

4.

1. From the Usability team - we want this to pass!

2. Needs a blank default option for type. Pass

3. Unanimously positive responses about this ticket after sharing it on the list. However, it would be a lot of work. Maybe put it on the community developer list?

4. This ticket is very thorough and Usability met with her to try to make mock ups. Unfortunately, none of us are that artistically talented. Is there enough info for developers to at least start making improvements on? We’d love for it to pass.

1. Move to Awaiting More Information and lower to Trivial. This requires a revisit to what should happen as a solution.

2. Pass

3. ?

4. Pass

@Daniel Michelson

1. Reproduced on 2.7. RDE button should be removed. Recommend passing, but reducing priority to trivial, since it doesn’t cause any problems.

2. Main entry is only relevant for MARC XML export, as EAD does not make this distinction. Current mapping is that the first agent listed as creator is exported as the main entry (1xx field). In the absence of any explicit need for having the main entry status applied prior to export, I recommend passing as trivial or closing.

3. This seems to have been resolved, probably as part of Lora’s update. Recommend closing as done.

4. This ticket provides a very clear (and referenced!) explanation of the usability problem with the current display of the digital object button in the PUI and mocks up two options for addressing the issue. The cited sources provide greater support for the hyperlink option (no. 1) compared to the button option (no. 2). Unless there is a need to retain the button style for consistency with other site elements, I recommend choosing option 1 and passing.

1. Pass

2. Close. No change. @Daniel Michelson to comment why.

3. Close as complete. Not relevant.

4. Pass option 1. Restate as a comment the differences between options.

[LT update: status changed, pending comment from Daniel]

@Alicia Detelich

@Lori Dedeyan (Unlicensed)

1. Unless there is a specific reason why Location Profiles and Event records are not directly editable from a list of results, I recommend implementing this request.

2. Agree that this issue should be addressed. All notes should obey user publication preferences by default. Beyond that, when tailoring at the archival object level in RDE, the decision to make is whether to have all fields obey publish/unpublish uniformly or to provide publish/unpublish option for every note field. I would support having an option for Note 1/2/3, if viable.

3. I haven’t been able to replicate this but agree that extent_number should export along with extent_type in CSV.

1. Pass

2. Pass with implementing options 1 and 3.

[LT update: status changed, pending Lori comment]

3. Close. This is no longer an issue.

@Laney McGlohon (Unlicensed) / @Lora Woodford

1. Pull request submitted - . Waiting for code review

2. Already implemented with pull request

1. This will be closed. No need to touch.

2. Closed-completed