World of Persistent Identifiers [Updated]

The reason I created this diagram was so I could visualise what the relationship is between Handles and DOIs, as well as other persistent identification systems.  This diagram has also helped colleagues, so I thought it was worth updating.

The Diagram for the World of Persistent Identifiers has been updated to include the OUR Journal service (Otago University Research Journal service).

Access the first version of this diagram World of Persistent Identifiers.

Setting up CrossRef DOIs in OJS

When looking at the requirements for implementing CrossRef DOIs (digital object identifiers) in OJS (open journal systems) I was uncertain of the order required to set this up. (It did not help that the terminology used by OJS, CrossRef and other resources varies.)

There are different OJS forum posts that cover this, like Re: STEP BY STEP FOR USING CROSSREF.  These posts did help me figure out most of the steps and code I have used. However, I still needed to figure out the right order for when you display a DOI and then when it should be activated (so it can be used as a link).

The order for setting up DOIs in OJS for a journal are:

1. Apply to CrossRef and receive a DOI prefix
2. Add this DOI prefix to the Journal Setup / Details page
3. Enter/select and save your preferred DOI suffix 
4. Alter the metadata displayed on the Article record page. This should include the DOI you generated. 
5. Once the article is Published/Live/Public submit the metadata and DOI to CrossRef.  Either use the CrossRef XML export plugin or submit to CrossRef manually via the form http://www.crossref.org/webDeposit/ 
6. CrossRef will activate the DOIs, using your submitted metadata/DOI. (There may be a delay in the activation but the DOI can still be cited.)

More details for some of these steps and code

2. Adding and generating your DOI for each article

• Go to - User Home / Journal Manager /  Journal Setup / 1. Details / 1.1 General Information / DOI Prefix.  Enter the prefix here

3. Create the DOI suffix for each journal.

• You can use the template structure with OJS or create a structure.  (The DOI structure I suggested for each journal was concise and human readable.)  CrossRef provides some guidance http://help.crossref.org/#establishing_a_doi_suffix_pattern

4. Alter the metadata displayed on the Article record page (i.e. Journal Initials, Volume, Issue, Year)

• The OJS default does not display metadata that CrossRef requires, so you will need to change what is displayed for each article.
• OJS provides support to help you figure out how to create or change the code: OJS API Reference http://pkp.sfu.ca/ojs/doxygen/current/html/index.html and go to the Class List
• Within the directory (file structure) for your journal go to: Templates / Article and open the article.tpl file (via an XML editor, but I found WordPad is enough to edit the file). I added this code under the Authors and above the Abstract.  Edit or order this based on the needs of each journal.

      <div>  
      <br />  
      <div><h4>{$journal->getLocalizedInitials()|escape}, Vol {$issue->getVolume()|escape}, No {$issue->getNumber()|escape} ({$issue->getYear()|escape}) </h4></div>  
      <div><a href="http://dx.doi.org/{$article->getStoredDOI()|escape}">http://dx.doi.org/{$article->getStoredDOI()|escape}</a></div>  
      <br />  
      </div>   

• If you do not want to display the DOI as a link before it is activated when you first set this up use the code for the DOI without the link

 <div>DOI: {$article->getStoredDOI()|escape}</div>  

World of Persistent Identifiers

We have been working on providing DOIs (Digital Object Identifiers) for some journals we are managing in OJS (Open Journal Systems). When I was trying to understand the relationship between the handles used by DSpace and different types of DOIs I wanted to visualise this. I also needed to cover options for persistency when managing data and archives. I ended up creating a diagram to help me picture the 'world of persistent identifiers'.

This diagram is a snapshot of what I was focusing on at the time of this investigation. If you want to remix this for your own purposes contact us and we can provide the original diagram (created in Microsoft Visio).

View the Updated version if this Diagram http://otagoliblab.blogspot.co.nz/2014/11/world-of-persistent-identifiers-updated.html.

Increasing the size of an EC2 root EBS volume

AWS EC2 AMI advertises that it comes with a 160G, but the loaded EBS only has 8G available. I only realised this once I started getting storage errors from my apps as the 8G cap was being hit. These are the steps I took to expand the root volume:

In the AWS console:

1. Create snapshot of the root volume (this will take a while)

2. Create a new volume from the snapshot with increased size (I put mine to 150G)

3. Stop the instance (you will get a warning about anything written to the ephemeral file system being lost. I lost my s3fs mount to S3. All my other data stayed)

4. Detach the root volume

5. Attach your new volume to the instance - set the device to /dev/sda1 (default root device)

6. Start up the Instance

7. If you had an elastic IP you will have to reattach that

8. ssh into your instance and, as root, run the following command:

resize2fs /dev/sda1

9. run df -h to see your newly super-sized (actually, the size it *should* have been from the start!) volume. You should see something like this:

Filesystem            Size  Used Avail Use% Mounted on

/dev/xvda1            148G  7.9G  139G   6% /

tmpfs                 830M     0  830M   0% /dev/shm