July 23, 2024 meeting notes

Resources:

Survey results: https://docs.google.com/presentation/d/1rU9M21IgwhSGh6YufxA7Iic7iWUaPGQFm-hUBoHYTbw/edit?usp=sharing

Use case document: https://docs.google.com/document/d/173G2PXg-sP7pe1Xlo76FhqqcJnNxbu-UFmrWR-AbMHY/edit?usp=sharing

Behavior scenario use case document: https://docs.google.com/document/d/1HoKKWqmHpqGQKMK4dQQiQMw2MnoR-7pdTtxt9IVqyKY/edit#heading=h.3mdvo5778nqs

Specification template: https://docs.google.com/document/d/1BZGoAlOCHmfeOdugMhJBBkQXNzOYHw3tTk9Y5SGL4lQ/edit?usp=sharing

Jira ticket template: Behavior Scenarios

5 min

Welcome

Jessica/Everyone

30 min

Discussion of use cases and spec

All

• Cory very helpfully added a behavior scenario to the use case document for RTL functionality. This wasn’t initially part of the scope of the work so the addition was very well received and this gets us ahead of the game on that particular requirement. The ticket for that functionality is at https://archivesspace.atlassian.net/browse/ANW-1144 The behavior scenario is linked above.

• There is concern that certain sub-records like extents and dates, which are repeatable fields that impact other application functionality, may be more complex than other functions. For now, the team will move forward knowing this may be a complication but for now the primary focus is on how multi-lingual description will look and feel in the PUI/SUI.

• One thing to keep in mind is that what we are talking about is not repeating fields in the application but representing the same field in multiple languages. The fields will not be “repeated,” just represented different ways.

• One major piece of functionality to discuss is how will a user select their preferred language.

15 min

Where do we go from here?

Everyone

See below

10
min

Next steps and action items?

Next meeting: August 27, 2024