WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsAs part of the SDMoM work, I need to create a new authority for Collecting Event. As I start this, I wanted to run my plan against everyone to see if I have all of the pieces (admittedly minus the tests, at this point).
In CSpace Application, create:
a) tomcat-main/src/main/resources/defaults/base-authority-collectingevent.xml [1]
b) tomcat-main/src/main/resources/defaults/domain-authority-collectingevent.xml [2]
c) tomcat-main/src/main/resources/defaults/extensions/anthro-authority-collectingevent.xml
In CSpace Services:
a) copy an existing service (say, 'services/taxonomy') to services/collectingevent and modify as needed
b) modify services/build.xml and services/pom.xml to add the new service point
c) modify services/JaxRsServiceProvider/pom.xml to add the new service point
In CSpace UI:
a) create src/main/webapp/defaults/html/pages/CollectingeventTemplate.xml
Some footnotes:
[1] - Since this is an extension geared towards anthropology, should I bother with a base-authority-collectingevent.xml file? Or just make one that is effectively just an opening and closing XML tag and put all of the anthropology stuff in anthro-authority-collectingevent?
[2] - Side note: why are there mostly empty domain-.xml files for all base-.xml files in application/tomcat-main/src/main/resources/defaults?
Have I missed anything?
Peter Murray
Dev/Ops Lead and Project Manager
Cherry Hill Company
One thing that jumps out, Peter: Taxonomy has just enough
weirdness/inconsistency to make it unsuitable as a base authority for a
'clone and update,' when creating a new authority.
If it turns out that you do embark on this work (following others'
comments, as well), perhaps you might use the Concept Authority as your
base? That one's fairly modern - and standard - from what I recall ...
Also, it looks like there was some functional/definition work around
Collecting Event here, so that might be a great place to start, when
developing SDMoM's schema and proposing a new community schema:
https://wiki.collectionspace.org/display/collectionspace/Collecting+Event+Authority+Schema
(see the comments, as well)
Aron
On Fri, Sep 25, 2015 at 2:25 PM, Peter Murray pmurray@chillco.com wrote:
As part of the SDMoM work, I need to create a new authority for Collecting
Event. As I start this, I wanted to run my plan against everyone to see if
I have all of the pieces (admittedly minus the tests, at this point).
In CSpace Application, create:
a)
tomcat-main/src/main/resources/defaults/base-authority-collectingevent.xml
[1]
b)
tomcat-main/src/main/resources/defaults/domain-authority-collectingevent.xml
[2]
c)
tomcat-main/src/main/resources/defaults/extensions/anthro-authority-collectingevent.xml
In CSpace Services:
a) copy an existing service (say, 'services/taxonomy') to
services/collectingevent and modify as needed
b) modify services/build.xml and services/pom.xml to add the new
service point
c) modify services/JaxRsServiceProvider/pom.xml to add the new service
point
In CSpace UI:
a) create
src/main/webapp/defaults/html/pages/CollectingeventTemplate.xml
Some footnotes:
[1] - Since this is an extension geared towards anthropology, should I
bother with a base-authority-collectingevent.xml file? Or just make one
that is effectively just an opening and closing XML tag and put all of the
anthropology stuff in anthro-authority-collectingevent?
[2] - Side note: why are there mostly empty domain-.xml files for all
base-.xml files in application/tomcat-main/src/main/resources/defaults?
Have I missed anything?
Peter Murray
Dev/Ops Lead and Project Manager
Cherry Hill Company
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Jumping in to say that we've developed a new draft schema for Collecting Event, and I still need to update the wiki page Aron references below. SDMoM is using this updated draft.
Sent from my iPhone
On Sep 25, 2015, at 5:38 PM, Aron Roberts <aron@socrates.berkeley.edumailto:aron@socrates.berkeley.edu> wrote:
One thing that jumps out, Peter: Taxonomy has just enough weirdness/inconsistency to make it unsuitable as a base authority for a 'clone and update,' when creating a new authority.
If it turns out that you do embark on this work (following others' comments, as well), perhaps you might use the Concept Authority as your base? That one's fairly modern - and standard - from what I recall ...
Also, it looks like there was some functional/definition work around Collecting Event here, so that might be a great place to start, when developing SDMoM's schema and proposing a new community schema:
https://wiki.collectionspace.org/display/collectionspace/Collecting+Event+Authority+Schema
(see the comments, as well)
Aron
On Fri, Sep 25, 2015 at 2:25 PM, Peter Murray <pmurray@chillco.commailto:pmurray@chillco.com> wrote:
As part of the SDMoM work, I need to create a new authority for Collecting Event. As I start this, I wanted to run my plan against everyone to see if I have all of the pieces (admittedly minus the tests, at this point).
In CSpace Application, create:
a) tomcat-main/src/main/resources/defaults/base-authority-collectingevent.xml [1]
b) tomcat-main/src/main/resources/defaults/domain-authority-collectingevent.xml [2]
c) tomcat-main/src/main/resources/defaults/extensions/anthro-authority-collectingevent.xml
In CSpace Services:
a) copy an existing service (say, 'services/taxonomy') to services/collectingevent and modify as needed
b) modify services/build.xml and services/pom.xml to add the new service point
c) modify services/JaxRsServiceProvider/pom.xml to add the new service point
In CSpace UI:
a) create src/main/webapp/defaults/html/pages/CollectingeventTemplate.xml
Some footnotes:
[1] - Since this is an extension geared towards anthropology, should I bother with a base-authority-collectingevent.xml file? Or just make one that is effectively just an opening and closing XML tag and put all of the anthropology stuff in anthro-authority-collectingevent?
[2] - Side note: why are there mostly empty domain-.xml files for all base-.xml files in application/tomcat-main/src/main/resources/defaults?
Have I missed anything?
Peter Murray
Dev/Ops Lead and Project Manager
Cherry Hill Company
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Thanks for the thoughts, Aron. As Megan said, we're working from a more advanced draft of the authority. It is still quite drafty, so I hesitate to put it up on the wiki, but I'll include a version of it here.
Peter
On Sep 25, 2015, at 5:38 PM, Aron Roberts aron@socrates.berkeley.edu wrote:
One thing that jumps out, Peter: Taxonomy has just enough weirdness/inconsistency to make it unsuitable as a base authority for a 'clone and update,' when creating a new authority.
If it turns out that you do embark on this work (following others' comments, as well), perhaps you might use the Concept Authority as your base? That one's fairly modern - and standard - from what I recall ...
Also, it looks like there was some functional/definition work around Collecting Event here, so that might be a great place to start, when developing SDMoM's schema and proposing a new community schema:
https://wiki.collectionspace.org/display/collectionspace/Collecting+Event+Authority+Schema https://wiki.collectionspace.org/display/collectionspace/Collecting+Event+Authority+Schema
(see the comments, as well)
Aron
On Fri, Sep 25, 2015 at 2:25 PM, Peter Murray <pmurray@chillco.com mailto:pmurray@chillco.com> wrote:
As part of the SDMoM work, I need to create a new authority for Collecting Event. As I start this, I wanted to run my plan against everyone to see if I have all of the pieces (admittedly minus the tests, at this point).
In CSpace Application, create:
a) tomcat-main/src/main/resources/defaults/base-authority-collectingevent.xml [1]
b) tomcat-main/src/main/resources/defaults/domain-authority-collectingevent.xml [2]
c) tomcat-main/src/main/resources/defaults/extensions/anthro-authority-collectingevent.xml
In CSpace Services:
a) copy an existing service (say, 'services/taxonomy') to services/collectingevent and modify as needed
b) modify services/build.xml and services/pom.xml to add the new service point
c) modify services/JaxRsServiceProvider/pom.xml to add the new service point
In CSpace UI:
a) create src/main/webapp/defaults/html/pages/CollectingeventTemplate.xml
Some footnotes:
[1] - Since this is an extension geared towards anthropology, should I bother with a base-authority-collectingevent.xml file? Or just make one that is effectively just an opening and closing XML tag and put all of the anthropology stuff in anthro-authority-collectingevent?
[2] - Side note: why are there mostly empty domain-.xml files for all base-.xml files in application/tomcat-main/src/main/resources/defaults?
Have I missed anything?
Peter
--
Peter Murray
Dev/Ops Lead and Project Manager
Cherry Hill Company