2024-05-07 Meeting notes

@Matthew Neely

Welcome

Meeting to focus on how Dev Pri can support @Thimios Dimopulos on community resources for Jira tickets.

All

Feedback on Jira templates for feature requests and bug reports

To test them out click on the create button on the project page: 

https://archivesspace.atlassian.net/jira/software/c/projects/ANW/boards/46  

and choose Bug or New Feature as issue type.

@Matt Strauss

Best practice on editing tickets discussion

@Tom Steele

Syntax highlighting of XML errors in staff interface does not catch attributes with no quote marks

1. Tested, it’s true it doesnt recognize missing quotes in a URL. Pass

@Mattie Clear

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

1. Confirmed Issue and agree that this would be a needed update. Currently the Digital Object module opens in a new tab, but any external links or internal links to other collections open in the same tab which could be confusing for users. Recommend passing. Carried over from last meeting.

   1. Added for March meeting: Brianna found a good resource from W3C school on guidelines for opening in a new tab and shared in a comment on the ticket. TLDR: best to open in same tab but if must open in new tab should have the little symbol with alt text stating that is what is happening. This symbol is already utilized within ASpace with regards to digital objects and so wouldn’t be foreign should we elect to do that. I believe that external doc and digital objects are the majority if not only examples of outside materials hyperlinked in ASpace, so it probably would be best to have those items handled uniformly?

@Cory Nimer

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

1. This appears to be working as anticipated based on ANW-1209 requirement 4. More information may be needed from the reporter to determine what change to the current functionality is desired.

@Dillon

@Alexander Duryee

@Bonnie Gordon

@Keli Schmid

@Brianna McLaughlin

@Matthew Neely

1. Previously reviewed for March 2024 Dev Pri meeting and was unable to replicate the issue. Contacted ticket creator to try and replicate their settings. Tried to replicate following update from ticket create but still not able to produce the error being reported. Recommend closing ticket as unable to replicate.

@Matt Strauss

Since submitting this ticket, Cambridge University Archives has implemented a solution and has indicated in the comments that others interested in this feature could email them for more details about their process.  I’ve confirmed that their fix sufficiently addresses their need.  Recommend closing.