to:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Working with multiple ASpace strings
We've got three (well four if you count my local dev) environments and follow a
pretty strict process of data always goes from prod -> other environments via a
db clone and
ot;
Reply-To: Archivesspace Group
Date: Thursday, May 30, 2019 at 6:12 AM
To: Archivesspace Group
Subject: Re: [Archivesspace_Users_Group] Working with multiple ASpace strings
We've got three (well four if you count my local dev) environments and follow a
pretty strict process of data always goes from pro
on.
Hope that helps!
Joshua
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Rees,
John (NIH/NLM) [E]
Sent: Wednesday, May 29, 2019 11:43 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Working
Hi all,
This question isn't aspace-centric, but for those of you that have multiple
deployment strings (dev, qa, production) and that use the PUI, what is your
best practice for entering new data or massaging existing data?
1. Do you test load/edit in QA then re-run the job in production?
