talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsadding dynamic lists to a tenant
I’ve got a clone of the LHMC tenant and am looking at domain-instance-vocabularies.xml (down in the source/applications/ ... /tenants hierarchy) to add a list of collection divisions.
According to https://wiki.collectionspace.org/display/DOC/How+to+add+a+dynamic+term+list,
the file ought to be bracketed by <instances> and </instances>, whereas the existing file (cloned from LHMC) is bracketed between <root> and </root> instead. I guess that the <instances> tags are read from default/extensions/culturalcare-vocabularies.xml, so all I have to do is slip my new instances in with the other ones?
I’ve tried adding an instance block along those lines but it doesn’t appear to have propagated through to the server.
ant complained that CSPACE_TENANT_CREATE_DISABLED_OPT didn’t exist so I created that as an environment variable set to “false”; ant then ran without complaint, cspace started up happily, but the term list still didn't propagate through.
What’s likely to be the problem?
And, thinking further ahead — suppose that I need to rebuild all this one day (quite likely, in fact, as we figure out new needs to customise for) — will new option values need to be entered into domain-instance-vocabularies.xml, to match what’s since been added via the CSpace web interface?
Alistair
--
Alistair Kwan
Centre for Learning & Research in Higher Education, University of Auckland
alistair.kwan@auckland.ac.nzmailto:alistair.kwan@auckland.ac.nz
Hi Alistair,
What you're doing sounds correct. You should be adding an <instance> block
in tenants/your_tenant_name/domain-instance-vocabularies.xml. I think it
actually doesn't matter what the root tag in that file is. Once you've done
that, rebuild the application layer, and restart tomcat.
That will update your configuration, but it won't create your new term
lists. To do that, follow the "Initializing default authorities and term
lists" instructions here:
https://wiki.collectionspace.org/display/DOC/Initializing+data
After that, you should see your new term lists.
Regarding updating domain-instance-vocabularies.xml to match what people
enter through the UI: My experience has been that if you rebuild the system
after people have started entering data, you don't just need to preserve
the term lists they've entered, you need to preserve all the other data as
well. So the easiest thing ends up being to dump the whole database,
restore it into your new system, and patch up schema changes (if any) with
SQL. Or if you run your database on a separate server, you can build your
new system and just point it at the same database.
Ray
On Sun, Jan 22, 2017 at 2:13 PM, Alistair Kwan <alistair.kwan@auckland.ac.nz
wrote:
I’ve got a clone of the LHMC tenant and am looking at
domain-instance-vocabularies.xml (down in the source/applications/ ...
/tenants hierarchy) to add a list of collection divisions.
According to https://wiki.collectionspace.org/display/
DOC/How+to+add+a+dynamic+term+list,
the file ought to be bracketed by <instances> and </instances>, whereas
the existing file (cloned from LHMC) is bracketed between <root> and
</root> instead. I guess that the <instances> tags are read from
default/extensions/culturalcare-vocabularies.xml, so all I have to do is
slip my new instances in with the other ones?
I’ve tried adding an instance block along those lines but it doesn’t
appear to have propagated through to the server.
ant complained that CSPACE_TENANT_CREATE_DISABLED_OPT didn’t exist so I
created that as an environment variable set to “false”; ant then ran
without complaint, cspace started up happily, but the term list still
didn't propagate through.
What’s likely to be the problem?
And, thinking further ahead — suppose that I need to rebuild all this one
day (quite likely, in fact, as we figure out new needs to customise for) —
will new option values need to be entered into domain-instance-vocabularies.xml,
to match what’s since been added via the CSpace web interface?
Alistair
--
Alistair Kwan
Centre for Learning & Research in Higher Education, University of Auckland
alistair.kwan@auckland.ac.nz
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_
lists.collectionspace.org
As of the v4.4 release (the current release) of CollectionSpace, you no longer need to explicitly initialize the authorities and term lists. Using the tenant credentials in the tenant's Application layer config, CollectionSpace will initialize them automatically the first time you login to your tenant/profile after a restart.
From: Talk talk-bounces@lists.collectionspace.org on behalf of Ray Lee rhlee@berkeley.edu
Sent: Wednesday, January 25, 2017 1:11 AM
To: Alistair Kwan
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] adding dynamic lists to a tenant
Hi Alistair,
What you're doing sounds correct. You should be adding an <instance> block in tenants/your_tenant_name/domain-instance-vocabularies.xml. I think it actually doesn't matter what the root tag in that file is. Once you've done that, rebuild the application layer, and restart tomcat.
That will update your configuration, but it won't create your new term lists. To do that, follow the "Initializing default authorities and term lists" instructions here: https://wiki.collectionspace.org/display/DOC/Initializing+data
After that, you should see your new term lists.
Regarding updating domain-instance-vocabularies.xml to match what people enter through the UI: My experience has been that if you rebuild the system after people have started entering data, you don't just need to preserve the term lists they've entered, you need to preserve all the other data as well. So the easiest thing ends up being to dump the whole database, restore it into your new system, and patch up schema changes (if any) with SQL. Or if you run your database on a separate server, you can build your new system and just point it at the same database.
Ray
On Sun, Jan 22, 2017 at 2:13 PM, Alistair Kwan <alistair.kwan@auckland.ac.nzmailto:alistair.kwan@auckland.ac.nz> wrote:
I’ve got a clone of the LHMC tenant and am looking at domain-instance-vocabularies.xml (down in the source/applications/ ... /tenants hierarchy) to add a list of collection divisions.
According to https://wiki.collectionspace.org/display/DOC/How+to+add+a+dynamic+term+list,
the file ought to be bracketed by <instances> and </instances>, whereas the existing file (cloned from LHMC) is bracketed between <root> and </root> instead. I guess that the <instances> tags are read from default/extensions/culturalcare-vocabularies.xml, so all I have to do is slip my new instances in with the other ones?
I’ve tried adding an instance block along those lines but it doesn’t appear to have propagated through to the server.
ant complained that CSPACE_TENANT_CREATE_DISABLED_OPT didn’t exist so I created that as an environment variable set to “false”; ant then ran without complaint, cspace started up happily, but the term list still didn't propagate through.
What’s likely to be the problem?
And, thinking further ahead — suppose that I need to rebuild all this one day (quite likely, in fact, as we figure out new needs to customise for) — will new option values need to be entered into domain-instance-vocabularies.xml, to match what’s since been added via the CSpace web interface?
Alistair
--
Alistair Kwan
Centre for Learning & Research in Higher Education, University of Auckland
alistair.kwan@auckland.ac.nzmailto:alistair.kwan@auckland.ac.nz
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org