Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

3:30 GMT / 11:30 ET / 10:30 CT / 9:30 MT / 8:30 PT

https://lyrasis.zoom.us/j/95479392806?pwd=S0FwbmpCbWVXT2RaTWhjUXhkMVFrZz09

Meeting ID: 954 7939 2806
Passcode: 965674
One tap mobile
+13126266799,,95479392806#,,,,,,0#,,965674# US (Chicago)
+19292056099,,95479392806#,,,,,,0#,,965674# US (New York)

Dial by your location
+1 312 626 6799 US (Chicago)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Germantown)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
877 853 5257 US Toll-free
888 475 4499 US Toll-free
Meeting ID: 954 7939 2806
Passcode: 965674
Find your local number: https://lyrasis.zoom.us/u/ahUXQvjfH

Participants

Goals

  • Prioritize new and awaiting more info tickets

Links

Kanban boards:

Link to ArchivesSpace sandbox: http://test.archivesspace.org/

Discussion topics

Topic/Who

Tickets

Notes

Decision

Angela White

  1. https://archivesspace.atlassian.net/browse/ANW-1131

  2.  https://archivesspace.atlassian.net/browse/ANW-1115

  3. https://archivesspace.atlassian.net/browse/ANW-1133

  1.  This should be pretty easy to do, but do we want to do it? Mine are organized in priority order in our instance, but I only have a handful.

  2. We passed this one last meeting, so yes! It seems like a good idea.

  3. This seems like a good way to make data cleanup easier--in addition to imports, most of the errors my students make is related to mis-categorizing subjects and agents.

Althea Topek

  1.  https://archivesspace.atlassian.net/browse/ANW-1122

  2. https://archivesspace.atlassian.net/browse/ANW-997

  3. https://archivesspace.atlassian.net/browse/ANW-1031

  1. I think this happens because the DO unique identifier doesn’t export in the xml so duplicate DOs can be created when importing.

  2. Is there enough information in this ticket to move forward?

  3. I didn’t have this experience while running other reports but there is a considerable amount of white space. Can this be cut down?

  1.  

  2.  

  3.  

Randy Kuehn

  1. https://archivesspace.atlassian.net/browse/ANW-857

  2. https://archivesspace.atlassian.net/browse/ANW-943

  3. https://archivesspace.atlassian.net/browse/ANW-484

  1. Recommend local plugin or push trivial if group decides it’s useful

  2. Recommend: pass
    Add ability to create MARC record from accession record to retain accession record details (provenance) and avoid duplicate work

  2.  

Daniel Michelson

  1. https://archivesspace.atlassian.net/browse/ANW-1064

  2. https://archivesspace.atlassian.net/browse/ANW-1093

  3. https://archivesspace.atlassian.net/browse/ANW-932

saron tran

  1. https://archivesspace.atlassian.net/browse/ANW-1079

  2. https://archivesspace.atlassian.net/browse/ANW-862

  3. https://archivesspace.atlassian.net/browse/ANW-363

Maggie Hughes

  1. https://archivesspace.atlassian.net/browse/ANW-765

  2. https://archivesspace.atlassian.net/browse/ANW-768

  3. https://archivesspace.atlassian.net/browse/ANW-746

Matthew Neely

  1. https://archivesspace.atlassian.net/browse/ANW-562

  2. https://archivesspace.atlassian.net/browse/ANW-773

  3. https://archivesspace.atlassian.net/browse/ANW-338

Action items

  •  

Decisions

  • No labels