Hi, Tim's right, it could be better documented, however the README file does mention it:
https://github.com/dspace/vagrant-dspace#usage-tips We would of course welcome any contributions to documentation on Vagrant-DSpace. Pretty much right now it's just the README file, and that's getting kinda big. Probably a space on the wiki could be created. Any volunteers? >From time to time this topic of a test dataset comes up, I do have some test >data I created from the data on demo.dspace.org. I also have a script written >which generates random metadata for bulk loading test metadata into dspace >[1]. I have heard of some people having test packages of Project Guttenberg >data/metadata... it would be a nice project to develop a test data set for >this use case, so we can build up some acceptance tests for automatically >validating DSpace builds. [1] https://github.com/hardyoyo/random_dspace_batch_metadata --Hardy ________________________________________ From: Tim Donohue [tdono...@duraspace.org] Sent: Friday, May 30, 2014 9:07 AM To: Monika Mevenkamp; dspace-devel@lists.sourceforge.net Subject: Re: [Dspace-devel] seed data for DSPACE [vagrant] instance Hi Monika, I believe Hardy Pottinger already added a way to "seed" 'vagrant-dspace' with a set of AIPs. It's a bit undocumented as of yet, though...but the code is here: https://github.com/DSpace/vagrant-dspace/blob/master/config/local-bootstrap.sh.example#L89 Essentially, you enable this "local-bootstrap" script by renaming it to "local-bootstrap.sh". Then, stick a bunch of AIPs in the empty "/content" folder on your source machine. Then, run your normal "vagrant up". The "local-bootstrap.sh" should load any AIPs in your local "/content" folder and prepopulate DSpace using those AIPs. Again, Hardy knows a bit more about this than I. I actually haven't had a chance to play with it much. But, I think that's the basics. - Tim On 5/29/2014 5:04 PM, Monika Mevenkamp wrote: > Now that I have vagrant-dspace up and running, I want to seed the > database with a test items/collections/communities. I had hoped that > the initial vagrant comes with a database filled test data. Alas, that > does not seem to be the case. > > How do you feel about adding a test database to vagrant along with > bitstreams in a test assetstore ? > > I volunteer to create an sql dump and related assetstore dir with > bitstreams - or does this already exist ? > Is there somebody who could then take that and integrate it into vagrant ? > This should be easy if you keep sql and assetstore files under git: > > dspace-src/test directory (or a separate git repo ?) > postgres/ > oracle/ > assetstore/ > > plus a provisioning step that uploads the SQL into dspacetest database > and a README explaining what to change in dspace.cfg to refer to the > test database and test assetstore > > of cause if the seed data is kept under git it can be used in other > places than just vagrant > > Monika > > ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
