...
We have been charged with leading a discussion for the December TAC Meeting
Topic Proposals:
Report out the tiers of metadata standards
Introduce our sample records in GitHub and exploring how we can use our repository to provide other services which are useful for the community
We can take on a documentation statement (which would be proposed before the agenda is finalized for the meeting)
This is a new sub-team, and we can use this is a time where we can request feedback or guidance from other members of the TAC
“This is what we are thinking, we would like TAC to kick this around…”
If there are needs for this sub-team, please note that it is appropriate to share these questions and concerns with the rest of TAC
Sharing path forward for exports, GitHub repos, what we have achieved thus far, and requesting feedback
We will have one more sub-team call scheduled before that meeting takes place
We should draft and finalize a paragraph outlining what we are going to address for the TAC meeting
All concurred with this
GitHub
Two presences on GitHub, a dedicated organization and a repository
...
Use organization, contact James for admin. privileges
Push ultimately to ArchivesSpace organization
James need to add Jared
...
James proposed that the GitHub Organization be used in order to develop the structure for the repositories
Once in a finalized state, these can be transferred to the ArchivesSpace Organization
Please freely contact James for access privileges on either the Organization or the repository
James needs to add Jared as an owner for the Organization
API access to the Sandbox
API access is provided for the sandbox ArchivesSpace installation (http://sandbox.archivesspace.org/)
James needs to provide documentation on working with authentication for the Sandbox (this should be located on https://github.com/ASpace-Metadata-Standards)
Workplan Review
Call for participating for the DACS tooltip review (Dan has volunteered to undertake this)
Test Processes for Importing Records
Testing and updating records using the import features
...
Proposal to take the import Excel, and place this into the Google Sheet where we can collectively comment and edit
ETA: Google sheet created and shared: https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit?usp=sharing
We begin confirming the behavior using our records
Any thoughts on using a Google Sheet to begin testing import mappings?
All agree, Kevin will set up the Google Sheets
With this we are ready to begin the testing process
Explicit about which version we are testing
2.7.2 had some new language updates, and we should note which test instances we are using
Kevin will distribute a Google Doc outlining this process to the community
Dan volunteered the DACS tooltip review
Scoped out and ready by the next meeting
Most of the work is just scoping for right now, just outlining the steps
Testing Strategy
Focusing on import initially
Leave export testing for the second half of the year
Additional Items
(No other additional items were proposed)
Meeting adjourned at 15:40EST