Page Comparison

Welcome

Updates?

DevPri input

• DevPri asked us to review this ticket:

  Jira Legacy
  server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1912

  . Thoughts? .

  • We agreed that standardizing the language to DACS-compliant YYYY-YYYY, bulk is the best solution. Brian brought up the idea of having tooltips in the PUI that would allow users to hover over to explain any archives jargon. Susannah will respond to ticket.

Jira tickets drafts

• Noah submitted the Jira ticket for the View button issues(

  Jira Legacy
  server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2246

  )

• Kelly- auto-saving in RDE?

  • A draft is in Google Drive - the group will review it at the next meeting

• Chris-Validate Only to import in bulk importer

Agents

• Continued to discuss the layout of name usage and dates in the PUI in Jira ticket 1811. The group will work on a mock-up of a new layout

  Jira Legacy
  server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1811

Other projects?

• • Working on it!

Brian asked the group for ideas for specific things in the yml and/or the config files that we would think archivists would like to have control over (instead of sys admins). We will discuss this exciting idea at our next meeting.

Other projects?

Other topics

Noah emailed the group this re: DevPri server - Also, in looking more closely into the test server we talked about last month, this is what the Dev Pri team was using: https://test.archivesspace.org/.  Anyone can access the staff interface with the username and pw “admin” like the sandbox. I think the difference is that the sandbox is more public-facing and offers current and prospective ArchivesSpace users the chance to try things out in the current release version, while the test server isn't versioned and is used for more internal testing by the Testing and Dev Pri Sub-Teams among other groups. For our purposes, I think we could test in either space, though the sandbox may be better if trying to replicate issues submitted from ArchivesSpace community members.

Re: if there any EAD (or other) reasons why there isn’t a box-level option in the Level of Description field controlled value list. The values are prescribed by the EAD schema (according to the help floating text.). (My notes had it as the Resource Type controlled value list, so if I looked into the wrong issue, please let me know!)