You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The performance of the main Archivist it slow because of the amount of content in there. The plan is to have one Archivist act as an archive which contains everything which is in Discovery, then have smaller instances which only contain work-in-progress.
Clone main Archivist instance to hold Discovery content as an archive @spuddybike
Load all Discovery instruments from all instances into new archive instance
- [ ] check list of exported content from Archivist (Jenny's script output)
- [ ] use Jenny's script to load instruments, (do we want to also move the datasets and mappings, the final version of these are on the dev server?) @jli755
Rename main Archivist to 'ucl' for wip (~80) @spuddybike
Export and re-load remaining wip instruments, datasets and mappings @HayleyMills
- [ ] from genscotland, heaf, onsls, wirral to 'lps'
- [ ] from alspac to 'lps'
- [ ] BCS, NCDS, NS, MCS, NSHD to remain in 'ucl'
- [ ] ALSPAC, WHII, SWS, HCS, from main to 'lps'
Update Airtable with correct IDs @HayleyMills (need a list of before and after IDs)
The text was updated successfully, but these errors were encountered:
@spuddybike can I check this process above is still the plan or are we simply saving all files in Discovery, rather than moving them to another instance?
I think we should export the files and have that as a backup as we will just end up having an unusable instance if we have an Archivist archive instance. We should I think put it on the S drive. JonOn 21 May 2024, at 09:56, HayleyMills ***@***.***> wrote:
@spuddybike can I check this process above is still the plan or are we simply saving all files in Discovery, rather than moving them to another instance?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
The performance of the main Archivist it slow because of the amount of content in there. The plan is to have one Archivist act as an archive which contains everything which is in Discovery, then have smaller instances which only contain work-in-progress.
- [ ] check list of exported content from Archivist (Jenny's script output)
- [ ] use Jenny's script to load instruments, (do we want to also move the datasets and mappings, the final version of these are on the dev server?) @jli755
- [ ] from genscotland, heaf, onsls, wirral to 'lps'
- [ ] from alspac to 'lps'
- [ ] BCS, NCDS, NS, MCS, NSHD to remain in 'ucl'
- [ ] ALSPAC, WHII, SWS, HCS, from main to 'lps'
The text was updated successfully, but these errors were encountered: