Hi all, We recently developed a series of reports for the Phoebe A. Hearst Museum of Anthropology and would like to make them more generic and contribute them to the CollectionSpace project. We will follow up with some more specific information about the fields to include, but basically this would be a set of procedure-specific reports. For example, we would contribute one report that contains information about an Acquisition record and the collection objects related to it. We'd do another for the Loan In record, and so on. We are looking at the report specifications at http://wiki.collectionspace.org/display/collectionspace/Sample+Reports+for+Default+CSpace+Implementation However, we might not add all the fields listed there, in order to keep it simple and to get the contribution finished. We will put together more information and ask people for their feedback. I'd be interested to hear if MMI, SMK, and WAC already have developed their customized reports. Thanks, Chris

One consideration is that we will need to have a small but representative set of data to report on in whatever generic deployment these reports run on. Presumably demo.collectionspace.org? I have fantisized making a small demo "test collection" with a bunch of cute records and procedures installed. I was thinking of basing it on the board game Clue (aka Cluedo) http://en.wikipedia.org/wiki/Cluedo ... you know "Mr. Mustard, in the Kitchen, with the Candlestick". We could have a small location authority (with Kitchen, Drawing Room, etc.) and small set of collectionobjects ("Candlestick", "Revolver", "Rope", etc.), and so on. Unless we have some data, the reports will look pretty...sparse. John On Mon, Jul 15, 2013 at 11:43 AM, Chris Hoffman <chris_h@berkeley.edu> wrote: > Hi all, > > We recently developed a series of reports for the Phoebe A. Hearst Museum of Anthropology and would like to make them more generic and contribute them to the CollectionSpace project. We will follow up with some more specific information about the fields to include, but basically this would be a set of procedure-specific reports. For example, we would contribute one report that contains information about an Acquisition record and the collection objects related to it. We'd do another for the Loan In record, and so on. We are looking at the report specifications at > > http://wiki.collectionspace.org/display/collectionspace/Sample+Reports+for+Default+CSpace+Implementation > > However, we might not add all the fields listed there, in order to keep it simple and to get the contribution finished. We will put together more information and ask people for their feedback. > > I'd be interested to hear if MMI, SMK, and WAC already have developed their customized reports. > > Thanks, > Chris > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

I seem to remember there was a script in the app layer that did this sort of thing, or maybe it was part of its API... I'm not sure how to invoke it anymore, or if it's been updated in some time, but it produced a good amount of dummy records. Oh yeah, don't forget to add the canonical "left-handed screwdriver" record. - Jesse On Mon, Jul 15, 2013 at 5:28 PM, John B. LOWE <jblowe@berkeley.edu> wrote: > One consideration is that we will need to have a small but > representative set of data to report on in whatever generic deployment > these reports run on. Presumably demo.collectionspace.org? > > I have fantisized making a small demo "test collection" with a bunch > of cute records and procedures installed. I was thinking of basing it > on the board game Clue (aka Cluedo) > > http://en.wikipedia.org/wiki/Cluedo > > ... you know "Mr. Mustard, in the Kitchen, with the Candlestick". We > could have a small location authority (with Kitchen, Drawing Room, > etc.) and small set of collectionobjects ("Candlestick", "Revolver", > "Rope", etc.), and so on. > > Unless we have some data, the reports will look pretty...sparse. > > John > > On Mon, Jul 15, 2013 at 11:43 AM, Chris Hoffman <chris_h@berkeley.edu> > wrote: > > Hi all, > > > > We recently developed a series of reports for the Phoebe A. Hearst > Museum of Anthropology and would like to make them more generic and > contribute them to the CollectionSpace project. We will follow up with > some more specific information about the fields to include, but basically > this would be a set of procedure-specific reports. For example, we would > contribute one report that contains information about an Acquisition record > and the collection objects related to it. We'd do another for the Loan In > record, and so on. We are looking at the report specifications at > > > > > http://wiki.collectionspace.org/display/collectionspace/Sample+Reports+for+Default+CSpace+Implementation > > > > However, we might not add all the fields listed there, in order to keep > it simple and to get the contribution finished. We will put together more > information and ask people for their feedback. > > > > I'd be interested to hear if MMI, SMK, and WAC already have developed > their customized reports. > > > > Thanks, > > Chris > > _______________________________________________ > > 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 >

I haven't done it in a while, but you can load a bunch of sample data using the app layer "reset" call: Initializing sample data (optional) You can optionally choose to initialize sample records. These sample records include a set of over 2,000 authority term records for persons and organizations. To do this, make sure you are logged in to either the core or lifesci tenant, then go to either or both of the following URLs: http://<ip-address>:8180/collectionspace/tenant/core/reset (for the core tenant, after logging into that tenant) http://<ip-address>:8180/collectionspace/tenant/lifesci/reset (for the lifesci tenant, after logging into that tenant) This process of adding sample data is time consuming - it can take 20 minutes or more. During that time, you will see a succession of progress messages in your browser window. Ray On Mon, Jul 15, 2013 at 2:49 PM, Jesse Martinez <mjesse@gmail.com> wrote: > I seem to remember there was a script in the app layer that did this sort > of thing, or maybe it was part of its API... I'm not sure how to invoke it > anymore, or if it's been updated in some time, but it produced a good > amount of dummy records. > > Oh yeah, don't forget to add the canonical "left-handed screwdriver" > record. > > - Jesse > > > On Mon, Jul 15, 2013 at 5:28 PM, John B. LOWE <jblowe@berkeley.edu> wrote: > >> One consideration is that we will need to have a small but >> representative set of data to report on in whatever generic deployment >> these reports run on. Presumably demo.collectionspace.org? >> >> I have fantisized making a small demo "test collection" with a bunch >> of cute records and procedures installed. I was thinking of basing it >> on the board game Clue (aka Cluedo) >> >> http://en.wikipedia.org/wiki/Cluedo >> >> ... you know "Mr. Mustard, in the Kitchen, with the Candlestick". We >> could have a small location authority (with Kitchen, Drawing Room, >> etc.) and small set of collectionobjects ("Candlestick", "Revolver", >> "Rope", etc.), and so on. >> >> Unless we have some data, the reports will look pretty...sparse. >> >> John >> >> On Mon, Jul 15, 2013 at 11:43 AM, Chris Hoffman <chris_h@berkeley.edu> >> wrote: >> > Hi all, >> > >> > We recently developed a series of reports for the Phoebe A. Hearst >> Museum of Anthropology and would like to make them more generic and >> contribute them to the CollectionSpace project. We will follow up with >> some more specific information about the fields to include, but basically >> this would be a set of procedure-specific reports. For example, we would >> contribute one report that contains information about an Acquisition record >> and the collection objects related to it. We'd do another for the Loan In >> record, and so on. We are looking at the report specifications at >> > >> > >> http://wiki.collectionspace.org/display/collectionspace/Sample+Reports+for+Default+CSpace+Implementation >> > >> > However, we might not add all the fields listed there, in order to keep >> it simple and to get the contribution finished. We will put together more >> information and ask people for their feedback. >> > >> > I'd be interested to hear if MMI, SMK, and WAC already have developed >> their customized reports. >> > >> > Thanks, >> > Chris >> > _______________________________________________ >> > 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 >> > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >

There is also a (non-documented?) API call to the app layer that I've seen used in the QA unit tests. It goes something like /collectionspace/tenant/core/intake /generator?quantity=1&startvalue=0&extraprefix=foo https://github.com/collectionspace/Tools/blob/master/qa-unittests/test/org/collectionspace/qa/Utilities.java#L140 On Mon, Jul 15, 2013 at 6:11 PM, Ray Lee <rhlee@berkeley.edu> wrote: > > I haven't done it in a while, but you can load a bunch of sample data > using the app layer "reset" call: > > Initializing sample data (optional) > > You can optionally choose to initialize sample records. These sample > records include a set of over 2,000 authority term records for persons and > organizations. To do this, make sure you are logged in to either the core > or lifesci tenant, then go to either or both of the following URLs: > > http://<ip-address>:8180/collectionspace/tenant/core/reset (for the core > tenant, after logging into that tenant) > > http://<ip-address>:8180/collectionspace/tenant/lifesci/reset (for the > lifesci tenant, after logging into that tenant) > This process of adding sample data is time consuming - it can take 20 > minutes or more. During that time, you will see a succession of progress > messages in your browser window. > > Ray > > > On Mon, Jul 15, 2013 at 2:49 PM, Jesse Martinez <mjesse@gmail.com> wrote: > >> I seem to remember there was a script in the app layer that did this sort >> of thing, or maybe it was part of its API... I'm not sure how to invoke it >> anymore, or if it's been updated in some time, but it produced a good >> amount of dummy records. >> >> Oh yeah, don't forget to add the canonical "left-handed screwdriver" >> record. >> >> - Jesse >> >> >> On Mon, Jul 15, 2013 at 5:28 PM, John B. LOWE <jblowe@berkeley.edu>wrote: >> >>> One consideration is that we will need to have a small but >>> representative set of data to report on in whatever generic deployment >>> these reports run on. Presumably demo.collectionspace.org? >>> >>> I have fantisized making a small demo "test collection" with a bunch >>> of cute records and procedures installed. I was thinking of basing it >>> on the board game Clue (aka Cluedo) >>> >>> http://en.wikipedia.org/wiki/Cluedo >>> >>> ... you know "Mr. Mustard, in the Kitchen, with the Candlestick". We >>> could have a small location authority (with Kitchen, Drawing Room, >>> etc.) and small set of collectionobjects ("Candlestick", "Revolver", >>> "Rope", etc.), and so on. >>> >>> Unless we have some data, the reports will look pretty...sparse. >>> >>> John >>> >>> On Mon, Jul 15, 2013 at 11:43 AM, Chris Hoffman <chris_h@berkeley.edu> >>> wrote: >>> > Hi all, >>> > >>> > We recently developed a series of reports for the Phoebe A. Hearst >>> Museum of Anthropology and would like to make them more generic and >>> contribute them to the CollectionSpace project. We will follow up with >>> some more specific information about the fields to include, but basically >>> this would be a set of procedure-specific reports. For example, we would >>> contribute one report that contains information about an Acquisition record >>> and the collection objects related to it. We'd do another for the Loan In >>> record, and so on. We are looking at the report specifications at >>> > >>> > >>> http://wiki.collectionspace.org/display/collectionspace/Sample+Reports+for+Default+CSpace+Implementation >>> > >>> > However, we might not add all the fields listed there, in order to >>> keep it simple and to get the contribution finished. We will put together >>> more information and ask people for their feedback. >>> > >>> > I'd be interested to hear if MMI, SMK, and WAC already have developed >>> their customized reports. >>> > >>> > Thanks, >>> > Chris >>> > _______________________________________________ >>> > 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 >>> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> >

Yes, I recall seeing "Marilyn Monroe" and "James Dean" go by on the loading of the sample person and org authorities. They would certainly be welcome additions to "L'Institut de Clue". But I am thinking of something a bit more elaborate. For reporting, esp. for a "report of each type", won't we need collection objects with related records of all types, and procedures in all their variegated glory? My suggestion is for a coherent collection for testing and reporting purposes, with Accessions in which "Colonel Mustard" is the Donor of "Scary Hobbit Mask", which in turn is related to a toy materials hierarchy containing "Gold", "Bamboo", and "Unobtanium". Colonel Mustard would have affiliations, no doubt, to an Organization like the "99th Royal New South Lilliputian Lancers<http://en.wikipedia.org/wiki/1st/15th_Royal_New_South_Wales_Lancers>", which in turn is a type of "Light Dragoon"... In short, a toy collectionspace world with enough goodies to get a decent report out of. The suggestions so far are great, just partial... On Mon, Jul 15, 2013 at 3:21 PM, Jesse Martinez <mjesse@gmail.com> wrote: > There is also a (non-documented?) API call to the app layer that I've seen > used in the QA unit tests. It goes something like > > /collectionspace/tenant/core/intake > /generator?quantity=1&startvalue=0&extraprefix=foo > > > https://github.com/collectionspace/Tools/blob/master/qa-unittests/test/org/collectionspace/qa/Utilities.java#L140 > > > On Mon, Jul 15, 2013 at 6:11 PM, Ray Lee <rhlee@berkeley.edu> wrote: > >> >> I haven't done it in a while, but you can load a bunch of sample data >> using the app layer "reset" call: >> >> Initializing sample data (optional) >> >> You can optionally choose to initialize sample records. These sample >> records include a set of over 2,000 authority term records for persons and >> organizations. To do this, make sure you are logged in to either the core >> or lifesci tenant, then go to either or both of the following URLs: >> >> http://<ip-address>:8180/collectionspace/tenant/core/reset (for the core >> tenant, after logging into that tenant) >> >> http://<ip-address>:8180/collectionspace/tenant/lifesci/reset (for the >> lifesci tenant, after logging into that tenant) >> This process of adding sample data is time consuming - it can take 20 >> minutes or more. During that time, you will see a succession of progress >> messages in your browser window. >> >> Ray >> >> >> On Mon, Jul 15, 2013 at 2:49 PM, Jesse Martinez <mjesse@gmail.com> wrote: >> >>> I seem to remember there was a script in the app layer that did this >>> sort of thing, or maybe it was part of its API... I'm not sure how to >>> invoke it anymore, or if it's been updated in some time, but it produced a >>> good amount of dummy records. >>> >>> Oh yeah, don't forget to add the canonical "left-handed screwdriver" >>> record. >>> >>> - Jesse >>> >>> >>> On Mon, Jul 15, 2013 at 5:28 PM, John B. LOWE <jblowe@berkeley.edu>wrote: >>> >>>> One consideration is that we will need to have a small but >>>> representative set of data to report on in whatever generic deployment >>>> these reports run on. Presumably demo.collectionspace.org? >>>> >>>> I have fantisized making a small demo "test collection" with a bunch >>>> of cute records and procedures installed. I was thinking of basing it >>>> on the board game Clue (aka Cluedo) >>>> >>>> http://en.wikipedia.org/wiki/Cluedo >>>> >>>> ... you know "Mr. Mustard, in the Kitchen, with the Candlestick". We >>>> could have a small location authority (with Kitchen, Drawing Room, >>>> etc.) and small set of collectionobjects ("Candlestick", "Revolver", >>>> "Rope", etc.), and so on. >>>> >>>> Unless we have some data, the reports will look pretty...sparse. >>>> >>>> John >>>> >>>> On Mon, Jul 15, 2013 at 11:43 AM, Chris Hoffman <chris_h@berkeley.edu> >>>> wrote: >>>> > Hi all, >>>> > >>>> > We recently developed a series of reports for the Phoebe A. Hearst >>>> Museum of Anthropology and would like to make them more generic and >>>> contribute them to the CollectionSpace project. We will follow up with >>>> some more specific information about the fields to include, but basically >>>> this would be a set of procedure-specific reports. For example, we would >>>> contribute one report that contains information about an Acquisition record >>>> and the collection objects related to it. We'd do another for the Loan In >>>> record, and so on. We are looking at the report specifications at >>>> > >>>> > >>>> http://wiki.collectionspace.org/display/collectionspace/Sample+Reports+for+Default+CSpace+Implementation >>>> > >>>> > However, we might not add all the fields listed there, in order to >>>> keep it simple and to get the contribution finished. We will put together >>>> more information and ask people for their feedback. >>>> > >>>> > I'd be interested to hear if MMI, SMK, and WAC already have developed >>>> their customized reports. >>>> > >>>> > Thanks, >>>> > Chris >>>> > _______________________________________________ >>>> > 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 >>>> >>> >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>> >>> >> >