First off, congrats, Elayne! On your patience, persistence, and on working through this latest issue (and all others earlier)! As I somewhat naively understand it, it's still preferable to use the merge with that very full 'base' file, and an 'actmuseum' file that reflects only your changes from the base. That way, when CollectionSpace upgrades apply: 1. You'll pick up any changes made to the base, over time, by the CollectionSpace development team/community. 2. You'll isolate - and hence more easily distinguish - any local changes you've made to the configuration. Would welcome others' perspectives here, especially from those who've performed such upgrades ... If at some point, you'd like some assistance identifying the merge issues, am hoping the collective wisdom on this list can also help with that. Congrats again! Aron On Thu, Apr 27, 2017 at 7:07 PM, Elayne Glantzberg < solinox@solinoxenterprises.com> wrote: > The first thing I needed to do was add a term to one of the static term > lists in base-collectionobject.xml. I tried creating a detail > atcmuseum-collectionobject.xml file and telling it to merge, like the > instructions say, but it crashed. So before you responded, what I did was > to copy the entire base-collectionobject.xml file into the atcmuseum tenant > directory, rename it atcmuseum-collectionobject.xml, add my term to the > list, and in the atcmuseum-tenant.xml settings file, I just swapped the > include statement from "base..." to "atcmuseum..." Then followed the > propagation and restart instructions as given on the webpage. That's > working for us now, I'm finally actually putting data into our system! > > Is this really poor practice, or can I keep working on it this way for > future customization changes? > > Elayne Glantzberg > Database Administrator > Aquarian Tabernacle Church >