Hi Monika, you can solve the chicken-egg problem using DSpace-CRIS, as you can generate the links to the datasets while submitting the publication, and DSpace-CRIS generates the reciprocal link (from the dataset to the publication) automatically, without the need for repository administrator to reopen the dataset items and manually add the link to the publication.
You can see an example of how it works here: https://dspace-cris.4science.it/handle/123456789/15 I hope this helps, Susanna Il giorno giovedì 28 febbraio 2019 15:23:10 UTC+1, Monika Mevenkamp ha scritto: > > We do too > > See a research data item HERE > <https://dataspace.princeton.edu/jspui/handle/88435/dsp01dz010s83s>. - > this is an example of a small data set > Neuro Science has sometimes huge datasets and I make researchers split > their data into multiple zip archives - see for example THERE > <https://dataspace.princeton.edu/jspui/handle/88435/dsp01pz50gz79z>. In > these situations users can not download all files with one click. With big > data sets researchers have to walk the line between 'not too many files’ > and 'none of the files is too big to be downloaded'. > > Then there is often a chicken and egg situation - researchers want the > permanent URL for their data set, so they can send it to publishers, but > they would also like to refer to the permanent URL of the published paper > in the dataset submission. We usually archive the data set first and tell > them to let us know when they have a publication URL, which we add on their > behalf to the data set. In another use case: researchers tell the > publishers about the permanent URL of the data collection, so they can > finalize data files by incorporating the publishers/editors feedback before > archival. We always try to impress on submitters that data sets should be > final. > > I have a standard email that I send to new submitters that explains what > they should be thinking about — see below > > Monika > > > > > Prof XXX, > > > I have set you up to submit to DataSpace [1]. I created an account so you > can submit content to the CEE Research Data Set collection > <https://dataspace.princeton.edu/jspui/handle/88435/dsp018049g519d> under > Civil and Environmental Engineering. Please let me know if this is not the > correct collection for your submission. > > Please keep in mind that content managed in DataSpace is made publicly > available on the Internet. Data files should be provided in commonly used > formats, so that users years from now will still be able to make sense of > the data. Princeton’s Library guide on Research Data Management [2] has > helpful information on data types and formats as well as recommendations on > file naming and structure. > > There is a limit to the data file size. Since DataSpace delivers files to > users via the HTTP protocol, big files can become problematic, especially > if the receiver does not have a fast Internet connection. On the other hand > you will not want to upload a very long list of files, since users would > have to download files one by one by clicking on each. Combining files in > tar/zip archive is a good way of bundling related data files. Several MBs > even several GBs per file are fine, please do try though to stay under > 10GB. > > We suggest to provide a ReadMe.txt file along with a short description of > the data sets and any other information users might need to successfully > use your data. Since most users will not download all files and we suspect > many will skip downloading the ReadMe.txt file, we suggest including it in > each tar/zip archive. In most cases reusing the same file everywhere should > be fine. > > To start your submission you need to log into DataSpace [1]. Once logged > in via the Central Authentication System, you will be redirected to your > 'My DataSpace' page. Click the green 'Start a new Submission' button. Next > Choose the collection you want to submit to. In your case you will have > exactly one choice, the CEE Research Data Set collection under Civil and > Environmental Engineering. > > After this you will move through several pages with forms; as usual you > need to enter values in fields marked with a star. Other fields are > optional. Please upload your files in the order that they should be > displayed. We suggest to start with the ReadMe.txt file. In the last step > please accept the license. For your reference I am including it at the end > of this message. The DataSpace system will send an email, once you accept > the license, to inform me about the submission. > > I will then perform a quick review and if everything looks good I will > make the submission public. The system assigns at that point a permanent > URL to your submission which you can share with your publisher. > > Looking forward to receiving your first submission, > > Monika > [1] http://dataspace.princeton.edu/jspui/mydspace > [2] http://libguides.princeton.edu/rdm > > > ----- > Monika Mevenkamp > [email protected] <javascript:> > https://mo-meven.mcmprogramming.com/wp > > > > On Feb 28, 2019, at 8:42 AM, [email protected] <javascript:> wrote: > > On Wednesday, February 27, 2019 at 3:44:43 PM UTC-5, David Bigwood wrote: >> >> Is anyone using DSpace as a repository for research data? Are you happy >> with your set-up? We need something to meet the new grant requirements. >> Comments welcomed. Even better pointers to your repository. Things to >> beware of, metadata fields needed, helpful tips all welcomed. >> > > > We do, and we're reasonably happy with it. > > https://dataworks.iupui.edu/ > > I'm just the guy who keeps it running, though, so I haven't much to say > about *how* we use it. We do have it connected with DataCite for automatic > DOI minting. > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://groups.google.com/group/dspace-community. > For more options, visit https://groups.google.com/d/optout. > > > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
