Hello, Can anyone tell me where I can find information on loading records into cspace? I think I am supposed to run a command to clean out our junk data, so we can import the clean data. Thanks so much, Al Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468

Hi Al, Running ant create_db in the services layer is the easiest way to delete everything and start off with an empty database. After this, you'll have to do the authorities/initialise step from the installation instructions, to recreate the authorities. If you also want to delete any users, roles, and permissions you've added, running ant import in the services layer will get you back to the initial state. Ray On Fri, Sep 20, 2013 at 2:31 PM, Al Bersch <abersch@museumca.org> wrote: > Hello, > > Can anyone tell me where I can find information on loading records into > cspace? I think I am supposed to run a command to clean out our junk data, > so we can import the clean data. > > Thanks so much, > > Al > > Al Bersch > Digital Project Coordinator > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >

Thanks, Ray! Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468 ----- Original Message ----- From: "Ray Lee" <rhlee@berkeley.edu> To: "Al Bersch" <abersch@museumca.org> Cc: "talk" <talk@lists.collectionspace.org> Sent: Friday, September 20, 2013 2:50:09 PM Subject: Re: [Talk] cleaning out sample/junk data from database prior to importing 'real' records Hi Al, Running ant create_db in the services layer is the easiest way to delete everything and start off with an empty database. After this, you'll have to do the authorities/initialise step from the installation instructions, to recreate the authorities. If you also want to delete any users, roles, and permissions you've added, running ant import in the services layer will get you back to the initial state. Ray On Fri, Sep 20, 2013 at 2:31 PM, Al Bersch < abersch@museumca.org > wrote: Hello, Can anyone tell me where I can find information on loading records into cspace? I think I am supposed to run a command to clean out our junk data, so we can import the clean data. Thanks so much, Al Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468 _______________________________________________ Talk mailing list Talk@lists.collectionspace.org http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Riffing on Ray's suggestions, especially since I'm not sure whether this is documented at this overview level anywhere: In the default CollectionSpace configuration, there are two databases: * 'cspace', which holds authentication/authorization (AuthN/AuthZ) data (e.g. users, roles, permissions ...) * 'nuxeo', which holds all other data (e.g. cataloging, procedural, and vocabulary-related records, relations between records ...) To clean the 'cspace' database: * From the top of the Services source code tree, run 'ant create_cspace_db' To then restore this database to a minimally useful state, by adding the default set of users, roles and access permissions for all configured tenants: * From the top of the Services source code tree, run 'ant import' To clean the 'nuxeo' database: * From the top of the Services source code tree, run 'ant create_nuxeo_db' To then restore this database to a minimally useful state, by creating authority records (e.g. the set of vocabularies in which authority terms can be created): * Follow the instructions in "Initializing data" (http://wiki.collectionspace.org/display/DOC/Initializing+data) (Note: you'll want to follow those steps in each active tenant. Alternately, you can run/adapt the script linked from that page to perform this task in every tenant, by running a single command.) To clean both databases at once: * From the top of the Services source code tree, run 'ant create_db' Aron P.S. To find out what Ant targets, if any, are available for you to run at any location within the Services, Application or UI source code trees, you can type 'ant -p'. On Fri, Sep 20, 2013 at 2:51 PM, Al Bersch <abersch@museumca.org> wrote: > Thanks, Ray! > > > Al Bersch > Digital Project Coordinator > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > ________________________________ > From: "Ray Lee" <rhlee@berkeley.edu> > To: "Al Bersch" <abersch@museumca.org> > Cc: "talk" <talk@lists.collectionspace.org> > Sent: Friday, September 20, 2013 2:50:09 PM > Subject: Re: [Talk] cleaning out sample/junk data from database prior to > importing 'real' records > > > Hi Al, > Running ant create_db in the services layer is the easiest way to delete > everything and start off with an empty database. After this, you'll have to > do the authorities/initialise step from the installation instructions, to > recreate the authorities. If you also want to delete any users, roles, and > permissions you've added, running ant import in the services layer will get > you back to the initial state. > > Ray > > > > On Fri, Sep 20, 2013 at 2:31 PM, Al Bersch <abersch@museumca.org> wrote: >> >> Hello, >> >> Can anyone tell me where I can find information on loading records into >> cspace? I think I am supposed to run a command to clean out our junk data, >> so we can import the clean data. >> >> Thanks so much, >> >> Al >> >> Al Bersch >> Digital Project Coordinator >> Oakland Museum of California >> 1000 Oak Street, Oakland, CA 94607 >> abersch@museumca.org >> 510-318-8468 >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

Thanks for the explanation, Aron. So if I wanted to get rid of a bunch of sample data we loaded, I would clean out the 'nuxeo' database by running 'ant create_nuxeo_db' from the top of the services code tree. Just to make sure I understand correctly. thanks, Al Al Bersch Digital Project Coordinator Oakland Museum of California 1000 Oak Street, Oakland, CA 94607 abersch@museumca.org 510-318-8468 ----- Original Message ----- From: "Aron Roberts" <aronroberts@gmail.com> To: "Al Bersch" <abersch@museumca.org> Cc: "Ray Lee" <rhlee@berkeley.edu>, "talk" <talk@lists.collectionspace.org> Sent: Friday, September 20, 2013 3:11:57 PM Subject: Re: [Talk] cleaning out sample/junk data from database prior to importing 'real' records Riffing on Ray's suggestions, especially since I'm not sure whether this is documented at this overview level anywhere: In the default CollectionSpace configuration, there are two databases: * 'cspace', which holds authentication/authorization (AuthN/AuthZ) data (e.g. users, roles, permissions ...) * 'nuxeo', which holds all other data (e.g. cataloging, procedural, and vocabulary-related records, relations between records ...) To clean the 'cspace' database: * From the top of the Services source code tree, run 'ant create_cspace_db' To then restore this database to a minimally useful state, by adding the default set of users, roles and access permissions for all configured tenants: * From the top of the Services source code tree, run 'ant import' To clean the 'nuxeo' database: * From the top of the Services source code tree, run 'ant create_nuxeo_db' To then restore this database to a minimally useful state, by creating authority records (e.g. the set of vocabularies in which authority terms can be created): * Follow the instructions in "Initializing data" (http://wiki.collectionspace.org/display/DOC/Initializing+data) (Note: you'll want to follow those steps in each active tenant. Alternately, you can run/adapt the script linked from that page to perform this task in every tenant, by running a single command.) To clean both databases at once: * From the top of the Services source code tree, run 'ant create_db' Aron P.S. To find out what Ant targets, if any, are available for you to run at any location within the Services, Application or UI source code trees, you can type 'ant -p'. On Fri, Sep 20, 2013 at 2:51 PM, Al Bersch <abersch@museumca.org> wrote: > Thanks, Ray! > > > Al Bersch > Digital Project Coordinator > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > ________________________________ > From: "Ray Lee" <rhlee@berkeley.edu> > To: "Al Bersch" <abersch@museumca.org> > Cc: "talk" <talk@lists.collectionspace.org> > Sent: Friday, September 20, 2013 2:50:09 PM > Subject: Re: [Talk] cleaning out sample/junk data from database prior to > importing 'real' records > > > Hi Al, > Running ant create_db in the services layer is the easiest way to delete > everything and start off with an empty database. After this, you'll have to > do the authorities/initialise step from the installation instructions, to > recreate the authorities. If you also want to delete any users, roles, and > permissions you've added, running ant import in the services layer will get > you back to the initial state. > > Ray > > > > On Fri, Sep 20, 2013 at 2:31 PM, Al Bersch <abersch@museumca.org> wrote: >> >> Hello, >> >> Can anyone tell me where I can find information on loading records into >> cspace? I think I am supposed to run a command to clean out our junk data, >> so we can import the clean data. >> >> Thanks so much, >> >> Al >> >> Al Bersch >> Digital Project Coordinator >> Oakland Museum of California >> 1000 Oak Street, Oakland, CA 94607 >> abersch@museumca.org >> 510-318-8468 >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >

Oh right, I should have said create_nuxeo_db where I said create_db. Ray On Fri, Sep 20, 2013 at 3:18 PM, Al Bersch <abersch@museumca.org> wrote: > Thanks for the explanation, Aron. So if I wanted to get rid of a bunch of > sample data we loaded, I would clean out the 'nuxeo' database by running > 'ant create_nuxeo_db' from the top of the services code tree. Just to > make sure I understand correctly. > > thanks, > > Al > > Al Bersch > Digital Project Coordinator > Oakland Museum of California > 1000 Oak Street, Oakland, CA 94607 > abersch@museumca.org > 510-318-8468 > ------------------------------ > *From: *"Aron Roberts" <aronroberts@gmail.com> > *To: *"Al Bersch" <abersch@museumca.org> > *Cc: *"Ray Lee" <rhlee@berkeley.edu>, "talk" < > talk@lists.collectionspace.org> > *Sent: *Friday, September 20, 2013 3:11:57 PM > > *Subject: *Re: [Talk] cleaning out sample/junk data from database prior > to importing 'real' records > > Riffing on Ray's suggestions, especially since I'm not sure whether > this is documented at this overview level anywhere: > > In the default CollectionSpace configuration, there are two databases: > * 'cspace', which holds authentication/authorization (AuthN/AuthZ) > data (e.g. users, roles, permissions ...) > * 'nuxeo', which holds all other data (e.g. cataloging, procedural, > and vocabulary-related records, relations between records ...) > > To clean the 'cspace' database: > * From the top of the Services source code tree, run 'ant create_cspace_db' > To then restore this database to a minimally useful state, by adding > the default set of users, roles and access permissions for all > configured tenants: > * From the top of the Services source code tree, run 'ant import' > > To clean the 'nuxeo' database: > * From the top of the Services source code tree, run 'ant create_nuxeo_db' > To then restore this database to a minimally useful state, by creating > authority records (e.g. the set of vocabularies in which authority > terms can be created): > * Follow the instructions in "Initializing data" > (http://wiki.collectionspace.org/display/DOC/Initializing+data) > (Note: you'll want to follow those steps in each active tenant. > Alternately, you can run/adapt the script linked from that page to > perform this task in every tenant, by running a single command.) > > To clean both databases at once: > * From the top of the Services source code tree, run 'ant create_db' > > Aron > > P.S. To find out what Ant targets, if any, are available for you to > run at any location within the Services, Application or UI source code > trees, you can type 'ant -p'. > > On Fri, Sep 20, 2013 at 2:51 PM, Al Bersch <abersch@museumca.org> wrote: > > Thanks, Ray! > > > > > > Al Bersch > > Digital Project Coordinator > > Oakland Museum of California > > 1000 Oak Street, Oakland, CA 94607 > > abersch@museumca.org > > 510-318-8468 > > ________________________________ > > From: "Ray Lee" <rhlee@berkeley.edu> > > To: "Al Bersch" <abersch@museumca.org> > > Cc: "talk" <talk@lists.collectionspace.org> > > Sent: Friday, September 20, 2013 2:50:09 PM > > Subject: Re: [Talk] cleaning out sample/junk data from database prior to > > importing 'real' records > > > > > > Hi Al, > > Running ant create_db in the services layer is the easiest way to delete > > everything and start off with an empty database. After this, you'll have > to > > do the authorities/initialise step from the installation instructions, to > > recreate the authorities. If you also want to delete any users, roles, > and > > permissions you've added, running ant import in the services layer will > get > > you back to the initial state. > > > > Ray > > > > > > > > On Fri, Sep 20, 2013 at 2:31 PM, Al Bersch <abersch@museumca.org> wrote: > >> > >> Hello, > >> > >> Can anyone tell me where I can find information on loading records into > >> cspace? I think I am supposed to run a command to clean out our junk > data, > >> so we can import the clean data. > >> > >> Thanks so much, > >> > >> Al > >> > >> Al Bersch > >> Digital Project Coordinator > >> Oakland Museum of California > >> 1000 Oak Street, Oakland, CA 94607 > >> abersch@museumca.org > >> 510-318-8468 > >> > >> _______________________________________________ > >> Talk mailing list > >> Talk@lists.collectionspace.org > >> > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >> > > > > > > > > _______________________________________________ > > Talk mailing list > > Talk@lists.collectionspace.org > > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > > >

What Ray said! :-) On Fri, Sep 20, 2013 at 3:24 PM, Ray Lee <rhlee@berkeley.edu> wrote: > Oh right, I should have said create_nuxeo_db where I said create_db. > > Ray > > > On Fri, Sep 20, 2013 at 3:18 PM, Al Bersch <abersch@museumca.org> wrote: >> >> Thanks for the explanation, Aron. So if I wanted to get rid of a bunch of >> sample data we loaded, I would clean out the 'nuxeo' database by running >> 'ant create_nuxeo_db' from the top of the services code tree. Just to >> make sure I understand correctly. >> >> thanks, >> >> Al >> >> Al Bersch >> Digital Project Coordinator >> Oakland Museum of California >> 1000 Oak Street, Oakland, CA 94607 >> abersch@museumca.org >> 510-318-8468 >> ________________________________ >> From: "Aron Roberts" <aronroberts@gmail.com> >> To: "Al Bersch" <abersch@museumca.org> >> Cc: "Ray Lee" <rhlee@berkeley.edu>, "talk" >> <talk@lists.collectionspace.org> >> Sent: Friday, September 20, 2013 3:11:57 PM >> >> Subject: Re: [Talk] cleaning out sample/junk data from database prior to >> importing 'real' records >> >> Riffing on Ray's suggestions, especially since I'm not sure whether >> this is documented at this overview level anywhere: >> >> In the default CollectionSpace configuration, there are two databases: >> * 'cspace', which holds authentication/authorization (AuthN/AuthZ) >> data (e.g. users, roles, permissions ...) >> * 'nuxeo', which holds all other data (e.g. cataloging, procedural, >> and vocabulary-related records, relations between records ...) >> >> To clean the 'cspace' database: >> * From the top of the Services source code tree, run 'ant >> create_cspace_db' >> To then restore this database to a minimally useful state, by adding >> the default set of users, roles and access permissions for all >> configured tenants: >> * From the top of the Services source code tree, run 'ant import' >> >> To clean the 'nuxeo' database: >> * From the top of the Services source code tree, run 'ant create_nuxeo_db' >> To then restore this database to a minimally useful state, by creating >> authority records (e.g. the set of vocabularies in which authority >> terms can be created): >> * Follow the instructions in "Initializing data" >> (http://wiki.collectionspace.org/display/DOC/Initializing+data) >> (Note: you'll want to follow those steps in each active tenant. >> Alternately, you can run/adapt the script linked from that page to >> perform this task in every tenant, by running a single command.) >> >> To clean both databases at once: >> * From the top of the Services source code tree, run 'ant create_db' >> >> Aron >> >> P.S. To find out what Ant targets, if any, are available for you to >> run at any location within the Services, Application or UI source code >> trees, you can type 'ant -p'. >> >> On Fri, Sep 20, 2013 at 2:51 PM, Al Bersch <abersch@museumca.org> wrote: >> > Thanks, Ray! >> > >> > >> > Al Bersch >> > Digital Project Coordinator >> > Oakland Museum of California >> > 1000 Oak Street, Oakland, CA 94607 >> > abersch@museumca.org >> > 510-318-8468 >> > ________________________________ >> > From: "Ray Lee" <rhlee@berkeley.edu> >> > To: "Al Bersch" <abersch@museumca.org> >> > Cc: "talk" <talk@lists.collectionspace.org> >> > Sent: Friday, September 20, 2013 2:50:09 PM >> > Subject: Re: [Talk] cleaning out sample/junk data from database prior to >> > importing 'real' records >> > >> > >> > Hi Al, >> > Running ant create_db in the services layer is the easiest way to delete >> > everything and start off with an empty database. After this, you'll have >> > to >> > do the authorities/initialise step from the installation instructions, >> > to >> > recreate the authorities. If you also want to delete any users, roles, >> > and >> > permissions you've added, running ant import in the services layer will >> > get >> > you back to the initial state. >> > >> > Ray >> > >> > >> > >> > On Fri, Sep 20, 2013 at 2:31 PM, Al Bersch <abersch@museumca.org> wrote: >> >> >> >> Hello, >> >> >> >> Can anyone tell me where I can find information on loading records into >> >> cspace? I think I am supposed to run a command to clean out our junk >> >> data, >> >> so we can import the clean data. >> >> >> >> Thanks so much, >> >> >> >> Al >> >> >> >> Al Bersch >> >> Digital Project Coordinator >> >> Oakland Museum of California >> >> 1000 Oak Street, Oakland, CA 94607 >> >> abersch@museumca.org >> >> 510-318-8468 >> >> >> >> _______________________________________________ >> >> Talk mailing list >> >> Talk@lists.collectionspace.org >> >> >> >> >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> >> > >> > >> > >> > _______________________________________________ >> > Talk mailing list >> > Talk@lists.collectionspace.org >> > >> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> > >> >

> Can anyone tell me where I can find information on loading records into cspace? Over time, here at UC Berkeley, my colleagues have built up local best practices and tools related to this task, on everything from data mapping from an existing collections management system to CollectionSpace, to data cleanup, to automating data loading. There are data cleanup scripts, ETL scripts (using Talend Studio), and even a 'meta' script (called "Magic Bus" :-) for managing multiple import runs. Other CollectionSpace implementers have also done so, as well, and they may well have practices, techniques and tools they've found particularly helpful. As a result, this Talk list would be a good place to once again discuss some of this. In summary, two of the more common ways of loading records involve: * Using the Imports service, for fast, bulk loading of records. * Using other parts of the Services REST APIs to selectively load records, or updates to existing records. As a starting point, the Imports service is documented here: http://wiki.collectionspace.org/display/collectionspace/Imports+Service+Home Here's a 'hello world'-type starting place: a 'curl' command and payload for loading a single object (Cataloging) record via the Imports service, into the 'core' tenant: curl -X POST http://localhost:8180/cspace-services/imports -i -u "admin@lifesci.collectionspace.org:Administrator" -H "Content-Type: application/xml" -T import_one_cataloging_record.xml where import_one_cataloging_record.xml consists of this payload: <?xml version="1.0" encoding="UTF-8"?> <imports> <import service="CollectionObjects" type="CollectionObject" CSID="be4797f1-08cf-4616-8a73-d763798f8ec3"> <schema xmlns:collectionobjects_common="http://collectionspace.org/services/collectionobject" name="collectionobjects_common"> <collectionobjects_common:objectNumber>UC15565</collectionobjects_common:objectNumber> </schema> </import> </imports> To try importing two Cataloging records at once, you can 'clone' the <import> block and change the CSID and objectNumber values in the second record. You can also import records of multiple types in a single import payload, if you choose. If you don't include the 'CSID=' attribute on any particular record, a random identifying number will be assigned to that record. Nonetheless, specifying CSIDs during import is often handy, especially if you want to create relations between records as part of the import process, etc. Aron On Fri, Sep 20, 2013 at 3:28 PM, Aron Roberts <aronroberts@gmail.com> wrote: > What Ray said! :-) > > On Fri, Sep 20, 2013 at 3:24 PM, Ray Lee <rhlee@berkeley.edu> wrote: >> Oh right, I should have said create_nuxeo_db where I said create_db. >> >> Ray >> >> >> On Fri, Sep 20, 2013 at 3:18 PM, Al Bersch <abersch@museumca.org> wrote: >>> >>> Thanks for the explanation, Aron. So if I wanted to get rid of a bunch of >>> sample data we loaded, I would clean out the 'nuxeo' database by running >>> 'ant create_nuxeo_db' from the top of the services code tree. Just to >>> make sure I understand correctly. >>> >>> thanks, >>> >>> Al >>> >>> Al Bersch >>> Digital Project Coordinator >>> Oakland Museum of California >>> 1000 Oak Street, Oakland, CA 94607 >>> abersch@museumca.org >>> 510-318-8468 >>> ________________________________ >>> From: "Aron Roberts" <aronroberts@gmail.com> >>> To: "Al Bersch" <abersch@museumca.org> >>> Cc: "Ray Lee" <rhlee@berkeley.edu>, "talk" >>> <talk@lists.collectionspace.org> >>> Sent: Friday, September 20, 2013 3:11:57 PM >>> >>> Subject: Re: [Talk] cleaning out sample/junk data from database prior to >>> importing 'real' records >>> >>> Riffing on Ray's suggestions, especially since I'm not sure whether >>> this is documented at this overview level anywhere: >>> >>> In the default CollectionSpace configuration, there are two databases: >>> * 'cspace', which holds authentication/authorization (AuthN/AuthZ) >>> data (e.g. users, roles, permissions ...) >>> * 'nuxeo', which holds all other data (e.g. cataloging, procedural, >>> and vocabulary-related records, relations between records ...) >>> >>> To clean the 'cspace' database: >>> * From the top of the Services source code tree, run 'ant >>> create_cspace_db' >>> To then restore this database to a minimally useful state, by adding >>> the default set of users, roles and access permissions for all >>> configured tenants: >>> * From the top of the Services source code tree, run 'ant import' >>> >>> To clean the 'nuxeo' database: >>> * From the top of the Services source code tree, run 'ant create_nuxeo_db' >>> To then restore this database to a minimally useful state, by creating >>> authority records (e.g. the set of vocabularies in which authority >>> terms can be created): >>> * Follow the instructions in "Initializing data" >>> (http://wiki.collectionspace.org/display/DOC/Initializing+data) >>> (Note: you'll want to follow those steps in each active tenant. >>> Alternately, you can run/adapt the script linked from that page to >>> perform this task in every tenant, by running a single command.) >>> >>> To clean both databases at once: >>> * From the top of the Services source code tree, run 'ant create_db' >>> >>> Aron >>> >>> P.S. To find out what Ant targets, if any, are available for you to >>> run at any location within the Services, Application or UI source code >>> trees, you can type 'ant -p'. >>> >>> On Fri, Sep 20, 2013 at 2:51 PM, Al Bersch <abersch@museumca.org> wrote: >>> > Thanks, Ray! >>> > >>> > >>> > Al Bersch >>> > Digital Project Coordinator >>> > Oakland Museum of California >>> > 1000 Oak Street, Oakland, CA 94607 >>> > abersch@museumca.org >>> > 510-318-8468 >>> > ________________________________ >>> > From: "Ray Lee" <rhlee@berkeley.edu> >>> > To: "Al Bersch" <abersch@museumca.org> >>> > Cc: "talk" <talk@lists.collectionspace.org> >>> > Sent: Friday, September 20, 2013 2:50:09 PM >>> > Subject: Re: [Talk] cleaning out sample/junk data from database prior to >>> > importing 'real' records >>> > >>> > >>> > Hi Al, >>> > Running ant create_db in the services layer is the easiest way to delete >>> > everything and start off with an empty database. After this, you'll have >>> > to >>> > do the authorities/initialise step from the installation instructions, >>> > to >>> > recreate the authorities. If you also want to delete any users, roles, >>> > and >>> > permissions you've added, running ant import in the services layer will >>> > get >>> > you back to the initial state. >>> > >>> > Ray >>> > >>> > >>> > >>> > On Fri, Sep 20, 2013 at 2:31 PM, Al Bersch <abersch@museumca.org> wrote: >>> >> >>> >> Hello, >>> >> >>> >> Can anyone tell me where I can find information on loading records into >>> >> cspace? I think I am supposed to run a command to clean out our junk >>> >> data, >>> >> so we can import the clean data. >>> >> >>> >> Thanks so much, >>> >> >>> >> Al >>> >> >>> >> Al Bersch >>> >> Digital Project Coordinator >>> >> Oakland Museum of California >>> >> 1000 Oak Street, Oakland, CA 94607 >>> >> abersch@museumca.org >>> >> 510-318-8468 >>> >> >>> >> _______________________________________________ >>> >> Talk mailing list >>> >> Talk@lists.collectionspace.org >>> >> >>> >> >>> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >> >>> > >>> > >>> > >>> > _______________________________________________ >>> > Talk mailing list >>> > Talk@lists.collectionspace.org >>> > >>> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> > >>> >>