Knowledgebase
6.2 Other ways to Share (URLs, DOIs)
Posted by Johan Isoz on 09 May 2017 03:54 PM

Increasingly, funding agencies (NSF, NIH, RCUK, ERC, etc.) require grant recipients to present a data plan and to publicly share portions of their project's data.  As a LabArchives user, you have several easy - and free - way to help you comply.
 
Sharing URLs

When you share notebook content, you have the option of sharing via an URL that links only to the specific content you want to share.

To obtain an URL for some content in your notebook, right-click that content where it appears in the Notebook Navigator (whether it is a page, subfolder, folder, or the entire notebook) and click "Share...". To share a single entry, hover your cursor over the entry where it appears on the page, and click "Share" from the set of buttons that appear in the upper left of the entry box.  When you do either of these things, the following window appears:


 

Copy and paste the link of the notebook/page entry. Whoever you email the links to will have access to that particular section of your notebook. As a rule, the recipient of the link will be able to navigate at that level and below in your notebook. For example, if you shared a link to a folder, then they would be able to navigate to everything in that folder. If you shared a link to a page entry, then they would only be able to see that entry.
 

Why use a DOI?

The advantage of using a DOI, rather than an URL, is that the DOI is indexed, in perpetuity, by the International DOI Foundation, of which LabArchives is a member.  While URLs may change or disappear, a DOI is permanent.  For example, if you are publishing a paper and want to include a supplemental data set, the DOI would be the preferred method.

You should use a DOI for instances in which you want to permanently share a set of data with the public.  Although you are empowered to remove the public rights to such data (under the Groups or People with Access tab), the DOI will still exist in cyberspace, so users who attempt to access your data will be denied.
 

How to make a DOI in LabArchives (For Professional Edition only)

When you click on the DOI Management tab, you will see the following:


 

Note that you may choose between sharing the following options:

1) The most recent version of this Entry (or Page, Folder or Notebook, depending on what you are sharing) or

2) The Entry (or Page, Folder or Notebook) as it exists at this moment in time.

Choosing the first selection allows you to share a DOI that exists as a living document; the people you share it with will see the most updated version of the shared content. Using the second will show it as it exists at this point in time.

So, in the example given above in which you are publishing a paper and want to share the data at the point, the paper was published, the second choice would be most appropriate. In general, a DOI should point to the data as it stood at the point in time when it was published.

Note that by checking the appropriate boxes, you can enable users to see earlier and/or later versions of your data.  This features provides for a "dynamic" publication of a dataset, so that a reader may first see the data as it stood at publication, but also past and future history of these data.

You should also enter the name of the author(s) and provide a Title and Publisher name for your dataset.  These fields, along with the data itself, will be searchable on the Internet through Google and other search services.


 

Note that assigning a DOI shares your data under Creative Commons Zero License agreement. After making your selection, simply click on the "Create DOI" button.  LabArchives will obtain a permanent, unique DOI;  after a few moments, the screen will appear as shown below with your new DOI:


 

You can publish this DOI as you desire.  Note that the viewing rights are still controlled by you as assigned in the "Groups or People with Access" tab;  if you want this DOI to be public, be sure to check the box marked "Allow anyone to view".

 
 

(2 vote(s))
Helpful
Not helpful

Comments (0)