Page Comparison

Retrospective for 2023-2024

2022-2023 Dev Pri Retrospective

Discuss and review Dev Pri’s work in 2023-2024

All to add comments by end of the week.

Tom Steele

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1452

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1683

1. Couldn’t replicate in 3.3.1 Is this issue already resolved?

2. This is an accessibility issue that I myself have had problems with. If one is unable to use a mouse, how can one reorder components? Pass.

1. Close (already resolved)

2. Pass

Matt Strauss

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1671

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-408

1. Confirmed this bug report. Also noticed the two other URLs in the root element are using “http” and being redirected to an “https” site. Pass.

2. This ticket encompasses two open subtasks and was last discussed by Dev/Pri in 2020.  One requests the ability to import XML accession data, which is waiting for a spec. The other requests the ability to import accession data with multiple subjects. There have been several recent comments in favor of this feature.  Previous comments suggest importing via XML could provide this capability.  Though multiple subjects/agents can currently be imported via the API, I’d recommend passing this given the community interest.

1. Pass

2. Close and convert subtasks to standalone tickets

Randy Kuehn

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1688

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-637

1. Four possible punctuation bugs identified related to MARC export - not entirely clear if the mistakes as due to export or input error

2. Pass - assuming related tickets (ANW-61, ANW-65, ANW-66, ANW-78, ANW-79) are still relevant

1. Ask Metadata Standards to confirm whether this is a bug

2. Pass

Matthew Neely

1.

2.

1. EAD exporter is using the old protocol for EAD which is re-directing to the current version. Metadata Standards have reviewed ticket and support the proposed change to the new protocol. Pass.

2. Metadata Standards have produced a specification for this following this ticket being reviewed by Dev Pri, 4 Oct 2022. Proposed spec is for the MARC XML Bibliographic (Resource) importer. If passed, additional tickets will be created for other import options. Recommend passing this.

1. Already discussed

2. Pass

Keli Schmid

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1726

2.

Daniel Michelson

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1710

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1704

1. Pass

2. • This ticket is ostensibly asking for the ability to make links in note fields open in a new window or tab via HTML encoding. I’m not sure if this is a misunderstanding by the submitter of the difference between XML encoding (which is partially supported) and HTML encoding (which is not supported). In any case, the way the system currently works is that using the <ref> tag causes the link to be opened in the current tab and using the <extref> tag causes the link to be opened in a new tab. The submitter noted that using <extref> instead of <ref> resolves the issue for them, but still likes the idea of having support for the ability to make that determination view HTML encoding.

   • I don’t see any reason why we’d allow HTML encoding, but I do understand why there might be a reason to allow more flexibility with the XML encoding in note fields. That said, I don’t think this is worth doing, since it’s such an edge case and I have a deep dislike for mixed content in note fields.

1. Pass

2. Close (will not do)

Next Meeting

Discuss possibility of July meeting or waiting until August for first meeting of 2023-2024 term.