Decide on process of moving ASpace records from staging to production

[marlo-longley]

Once we have final data formatted in staging ASpace, we will need to ask Michael Olsen to migrate it into production. He indicated the process was to request him.
We will also want to request a set of credentials that our app can use in production to connect to the API.
For production app creds should we only need the following permission level
view_repository

[marlo-longley]

Update: getting different info from Michael now. He is not sure of the migration process and may need dev support.

[marlo-longley]

We agree that our prod app will pull from prod ASpace server

[marlo-longley]

Michael let me know that he thinks the best way to promote data from stage to prod ASpace is to follow this guide for exporting EAD, and then importing it. He sent me the import instructions in a PDF.
https://kb.wisconsin.edu/uwlss/page.php?id=96630

This seems error prone to me. I am thinking the best path forward will be to directly import our data again to production. Thoughts? @thatbudakguy @laurensorensen

[thatbudakguy]

That guide seems like it has 20+ manual steps of editing EAD, which is not ideal. I think just reuploading the current data to prod is fine. In the future we should make sure that curators or whoever edits data in prod only, and we may need to figure out a better way to small chunks of data from prod into stage, but for now it should be OK.

[marlo-longley]

@thatbudakguy I agree.

I wonder though whether this will create a lot of extra work for @laurensorensen who is inputting scope and contents text currently to staging. To your point about future work being done in production. I'd be curious to hear from @laurensorensen if duplicating that work in production seems doable.

[marlo-longley]

We don't think manual entry in production will be too hard. Closing as decision is made.