Page Comparison

...

Item/Who

Tickets

Notes

Decision

Roll call

Discussion

Good responses on the following tickets shared by Lydia on the member list.

Topic emerged about how long it takes for tickets to be resolved. Here’s a new view of unresolved tickets sorted by the date they were created. To be equitable, perhaps we should tackle these in 2020 in this order?
Are we going to create a new kanban row for shuttling tickets that subteams need to review?
Clarification of Jira workflow: besides commenting on tickets, most team members don’t need to do much with Jira. Dev. Pri. co-chairs meet later in the week to move the tickets on the boards. Thanks to Daniel for catching if we move a ticket to the wrong position!

People have been commenting a lot, and helpfully. ANW-769 seems like it should be a priority.

Keep in Awaiting More Info.

2. Leave comment for Program Team to investigate whether it can be configurable (potential re-sizing issues). Move to Ready for Implementation.

3. Leave as is while the community continues to debate.

New Kanban board for sub-team review?

Q about how Metadata Standards should relay changes they recommend to the data maps?
Should we make official liaisons between Dev Pri and other sub-teams.
Will keep thinking about this.

Lydia emailed the listserv about how to create a Jira account.

Removal of “votes” on Jira tickets was a Jira change (not an ASpace decision). Still available in old version view. Who knows if it will come back? Watching function is helpful to be notified for changes to a ticket.

Tickets

Ticket theme for today’s meeting: mostly bugs and usability tickets

Lori Dedeyan (Unlicensed)

1.

2.

3.1

Close.

2. Change priority to Trivial. Ready for Implementation.

3. Leave comment that checkboxes for CSV export (and other CSV exports) should be split off into a new ticket. Move to Ready for Implementation with the caveat that it does not include the CSV export checkboxes.

Alicia Detelich

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

2. https://archivesspace.atlassian.net/browse/ANW-926 3. https://archivesspace.atlassian.net/browse/ANW-803

Unsure what to do with this one. Assuming this means the EAD/EAC/MARCXML schema, as any invalid AS record should already fail on import. Agree in principle but unclear about steps to implementation. Is there any existing validation against these standards or is it just the AS schema? Where do the two diverge? Recommend change to “Awaiting more information”

2. Followed steps in ticket but could not replicate in version 2.7.0 - already fixed? Tried both removing the instances and deleting the objects without removing the instances and all was ok.

3. Note from Christine in November 2018 indicates that Lora did some research into this - what was the result of that? Support passing the ticket but unsure what additional information is needed. Changing this seems trivial but would require a db migration1

Close.

2. Leave comment that we could no longer replicate the issue, sos we are closing iti, and to please re-open if issue persists. Close.

3. Lora is researching. Move to Ready for Implementation.

Lydia Tang (Unlicensed)

Usability looked at this and felt it was useful for both staff and PUI, to maximize the ability of dynamically generated finding aids.
Usability felt this was a useful feature. I forget if we discussed this and said the programming architecture is too complex to fix?
This is a new “bug” that would be nice to fix soon. Endorsed by Usability
Also endorsed by Usability
Also endorsed by Usability

1.

2.

3.
4.

Lydia Tang (Unlicensed) comment to focus only on PUI (not SUI) and that it needs more specification. Lora Woodford comment on what this work might look like (and that it can’t be done with infinite scroll). Lydia Tang (Unlicensed) to draft a ticket to get rid of infinite scroll. Move to Awaiting More Information.

2. Lydia Tang (Unlicensed) to modify ticket to remove adding it to the Container Inventory tab, and clarify that adding it to the Collection Organization. Move to Ready for Implementation.

3. Change priority to trivial. Move to Ready for Implementation.
4. Move to Ready for Implementation.

5.

Randy Kuehn

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

Confirmed typeahead does not accommodate hyphenated entries (v2.7.0)
Recommend: pass
Confirmed controlaccess title tags are skipped during EAD import (v2.7.0)
Recommend: pass

1.

2.

Daniel Michelson

https://archivesspace.atlassian.net/browse/ANW-951 2. https://archivesspace.atlassian.net/browse/ANW-958 3. https://archivesspace.atlassian.net/browse/ANW-946

Issue exists in 2.7. Solution requires changing the logic used to generate agents from user records. The simplest method would be to name the agent after the username, since that already has to be unique. Recommend changing priority to minor, adding the solution, and changing to ready for implementation.
Could not reproduce, submitter confirmed that this is not a problem anymore. Close as done.
Not clear this behavior is incorrect, commented asking for clarification.

1

Laney McGlohon (Unlicensed) will assign to Lora Woodford Move to Ready for Implementation.

2. Close as done.

3. Move to Awaiting More Information.

Maggie Hughes

https://archivesspace.atlassian.net/browse/ANW-555 2. https://archivesspace.atlassian.net/browse/ANW-894 3. https://archivesspace.atlassian.net/browse/ANW-851

Keep priority at minor. Add a note saying model off of agent/subject merging?Pass.
Thinking most <extref> would be within the text of a note (s&c, related materials, etc), not sure there is a need to map this to an EAD element. Close.
Confirmed in sandbox still an issue in v2.7.0. Pass.

1

Comment to repurpose container profile merging. Use check boxes and merge and be able to specify the survivor. Ready for Implementation.

2. Close.

3. Ready for Implementation.

Edgar Garcia (Unlicensed)

Jira Legacy
server System JIRA
columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId 36c489e2-4fb0-353a-985b-64038401be2f
key ANW-736
fixed the reorder issue.
1. Github issue to investigate removal of parent_name exists
2. Depending on Dev response, wait or abandon?
Cannot reproduce this issue, I have asked the reporter for reproduction steps.
1. Recommend we wait for more information.
From Christine: “For the 2.7.0 release we’ve now added a configuration option to the end of the Config file - AppConfig[:limit_csv_fields] . By default this is set to true, to limit the fields in those CSVs to selected columns on the screen. If you set it to false it will work the way it did previously”
1. Does 2.7.0 technically resolve this issue by allowing to revert to “old way”? If the case, I move to close this ticket for now.

1

Comment to say this is depenedent on the results of ANW-736. Move to Ready for Implmentation.

2. Move to Awaiting More Information and wait to hear more info from reporter.

3.

Laney McGlohon (Unlicensed)

Lora Woodford

https://archivesspace.atlassian.net/browse/ANW-805 2. https://archivesspace.atlassian.net/browse/ANW-918

Still need more information on this one

2. Move forward with Lora’s suggestion of a job to run

...

Versions Compared

Old Version 18

New Version 19

Key