Posts Tagged ‘research’

Throw down the SWORD

Posted on May 7th, 2013 by Paul Stainthorp

With the Orbital project at its end, and plans for a University research information / research data service afoot, I’m reviewing the excellent work carried out by our (now-departed) developers Harry Newton and Nick Jackson – work which linked up CKAN, the Orbital ’bridge’ application, and the Lincoln Repository (EPrints) using SWORD – described in earlier blog posts here and here.

“One important piece of work that we’re undertaking at the moment in Orbital is the facility to deposit the existence of a dataset, from CKAN and the University’s new Awards Management System (AMS), into our (EPrints) Repository via SWORD – at the same time requesting a DOI for the dataset via theDataCite API. The software at the centre of this operation is what we refer to as Orbital Bridge.”

This deposit workflow is now broadly working as it should – I think only a few tweaks would be necessary now to turn this into a working tool for the University of Lincoln.

Most urgent is the need for the University to sign up with the DataCite DOI service, which would secure a DOI for each dataset record deposited from CKAN and hence formally published by the University. This subscription should form part of the new research information service.

The underlying code could be used for other SWORD-enabled deposit from sources of metadata (e.g. the Library’s discovery system, Find it at Lincoln), to the Lincoln Repository as the University’s bibliographic ‘system of record’.

Warning: this is an extremely screenshot-heavy blog post! Click on any one of the screenshots below to view a larger image.

Here’s a step-by-step walkthrough of the entire process of adding a dataset to CKAN, and depositing it as a record in the Lincoln Repository.

  1. Go to the Researcher Dashboard at: https://orbital.lincoln.ac.uk/ and click on “Sign In”.
    Screenshot from the Researcher Dashboard
  2. Enter your staff accountID and password to sign in to the Researcher Dashboard.
    Screenshot from the Researcher Dashboard
  3. Once you have been signed in and returned to the Researcher Dashboard, click on your name (in the top right-hand corner) and then click on “My Projects”.
    Screenshot from the Researcher Dashboard
  4. You will see an overview of your research projects – both funded projects (derived from the AMS), and unfunded projects you have added locally. Click on the name of the project you want to add data to.
    Screenshot from the Researcher Dashboard
  5. You will be taken to a page for that research project. On the right-hand side of this page, under the heading “Options”, click on “Create Research Data Environment”.
    Screenshot from the Researcher DashboardImage7
  6. You will be taken to the University’s CKAN research data platform, where a page/group will have been created which corresponds to your project in the Researcher Dashboard. Sign in to CKAN using your staff accountID (there is currently no single sign-on between the Researcher Dashboard and CKAN) and password and you should be returned to the same page. However you will probably be sent instead to the CKAN home page, in which case you will have to look again for your project under the “Groups” menu.
    Screenshot from CKAN
  7. Toward the top of the project screen in CKAN, click on “Add Dataset” > “New Dataset…”.
    Screenshot from CKAN
  8. Fill in the form with information about the overall dataset, including the following fields:
    • Title
    • URL
    • License (N.B. US spelling!)
    • Description
      Screenshot from CKAN
  9. Then click on “Add Dataset”
    Screenshot from CKAN
  10. If you now click on “Further information” tab on the left-hand menu, you can add the following additional information about the dataset (this is not obvious from the initial dataset form):
    • Author
    • Author email
    • Maintainer
    • Maintainer email
    • Version
    • Summary [of changes]
      Screenshot from CKAN
  11. To attach individual data document(s)—which CKAN refers to as “resources”—to the dataset, scroll down the page and click on “Upload a file” (there are other options) > “Choose file” > “Upload”.
    Screenshot from CKAN
  12. Then fill in the form with the following basic information about the “resource”:
    • Name
    • Description
    • Format
    • Resource Type
    • Datastore enabled (ticked by default)
    • Mimetype
    • Mimetype (Inner)
    • “Extra Fields” (user-defined, or used by Orbital)
      Screenshot from CKAN
  13. To deposit a record for this dataset in the Lincoln Repository, go back to the Orbital Researcher Dashboard at: https://orbital.lincoln.ac.uk/ and navigate to your project. Toward the bottom left of the page you should now see a table containing the dataset(s) you have created in CKAN for this project. Choose which dataset you want to deposit, and hit the “Publish to Lincoln Repository” button.
    Screenshot from the Researcher Dashboard
  14. The Researcher Dashboard will then display a deposit form containing the following fields (some of which should be being autopopulated from CKAN fields but which do not appear to be):
    • Title
    • Description
    • Type of Data
    • Keywords
    • Subjects
    • Divisions
    • Metadata visibility [Show|Hide]
    • People
      Screenshot from the Researcher Dashboard
      “Publishing will publicly announce the existence of your dataset on the Lincoln Repository, as well as start the process of long-term preservation of your data.“Usually you should only publish a dataset either at the end of a research project, or if the data is being cited in a paper. Publishing a dataset will place some restrictions on the changes you can make to the dataset in the future, such as removing your ability to delete the data. It will also generate a DOI, which allows your dataset to be uniquely identified and located using a simple identifier.“Please check the information in this form and make any necessary changes, as this is the information which will be entered into the published record of the dataset.“If you have any questions about this process please contact a member of the research services team for advice or assistance.”
  15. When you hit the “Publish Dataset” button, the dataset record from CKAN will be used to create a record in the Lincoln Repository. The record will be submitted for review by the Repository team, who will then make it live. N.B. for the time being, you will see an error “Validation errors: [doi] is a required string“ – this happens because the University does not currently have access to the live DataCite DOI service, which would secure a DOI for each dataset record deposited from CKAN. This should form part of the new research information service.
    Screenshot from the Researcher Dashboard
  16. Here’s an example of a record in the Lincoln Repository, created from a CKAN dataset and made live by the Repository team.
    Screenshot from the Lincoln Repository

Problems with the deposit process as it currently stands:

  1. Permissions are not correctly cascaded from a project the Researcher Dashboard to a group in CKAN.
  2. There is currently no single sign-on between the Researcher Dashboard and CKAN.
  3. When CKAN challenges a user to log in to a group, they should be redirected back to the group page after logging in – instead they get sent back to the CKAN home page, in which case they will have to look again for their project under the “Groups” menu.
  4. A minor one – in CKAN ”License” (noun) appears in US spelling (should be “Licence”).
  5. In order to add all the information needed to deposit a dataset from CKAN, user has to click  ”Further information” tab on the left-hand menu (this is not obvious from the initial dataset form).
  6. Some of the field labels in CKAN are a bit opaque or use technical terms (“Mimetype”) which could do with explanation.
  7. When depositing to EPrints, some of the deposit fields should be being autopopulated from CKAN fields – this does not appear to be happening. The fields affected are:
    • “Description” (could be derived from CKAN dataset/resource Description fields)
    • “Type of Data” (could be derived from CKAN resource Format field)
  8. Repository records created from CKAN have the data “Creator” attached, but not the “Maintainer”.
  9. Repository records created from CKAN don’t have a link back to the CKAN dataset (should go in the EPrints “Official URL” field) – this will be required to provide access to the data.
  10. After deposit, users see the error message “Validation errors: [doi] is a required string” – the University does not currently have access to the live DataCite DOI service, which would secure a DOI for each dataset record deposited from CKAN.

Research data documentation and training materials

Posted on April 26th, 2013 by Paul Stainthorp

The final within-project version of the Orbital Research Data Management training materials are now live on the Orbital Researcher Dashboard website. They have been written collaboratively by the Orbital project team, and draw on a lot of existing RDM training and guidance material from across the web (in particular, from the DCC).

We intend that these materials will continue to be maintained and developed as part of the new University-wide research information service mentioned in a previous blog post.

The training materials can be accessed at https://orbital.lincoln.ac.uk/ and cover the following areas:

  1. Screenshot of the Researcher DashboardWhat is research data?
  2. The research data lifecycle
  3. Policies affecting your research data
  4. Data Management Planning (DMP)
  5. Data search and discovery tools
  6. Data storage and security
  7. Legal and ethical issues
  8. Tools for working with your data
  9. Data publishing and citation
  10. Licences for sharing your data
  11. Data curation and preservation
  12. Workshops and training events
  13. Help and support

The source text for each page is stored in an open Github repository (at http://github.com/unilincoln/rdm) in Markdown format. The page admin tools in the Researcher Dashboard can then be used to link to the source document, which is then formatted in the University’s Common Web Design.

These web pages will be used to support the ongoing RDM training for postgraduate students, which will shortly be rolled out to University staff.

Quarterly Research Output Report 2012 Q1

Posted on September 18th, 2012 by Paul Stainthorp

The latest Quarterly Research Output Report for the University of Lincoln has been produced, covering the period January–March 2012 inclusive.

These reports paper summarize research outputs published in each quarter by academic staff at the University of Lincoln. The lists include substantive research outputs first appearing “in published form” (or equivalent for non-textual outputs) during this period. The lists have been generated automatically from data stored in the Lincoln Repository (http://eprints.lincoln.ac.uk/). Tables summarize the volume of outputs recorded by School.

The quarterly reports are themselves available to download from the Repository, at: http://eprints.lincoln.ac.uk/5873/

Electronic Resources Librarian: priorities 2011/2012

Posted on November 17th, 2011 by Paul Stainthorp

I’ve had a useful meeting with my new boss to agree my priorities for the next 12 months of development work in the Library. Here are my top 4, in order of importance.

  1. Discovery selection & implementation;
  2. JISC Orbital project (0.3FTE) – based mainly in CERD until March 2013;
  3. Possible JISC-funded Jerome follow-on work;
  4. Development of the Lincoln Repository – working closely with the Library Institutional Repository Officer (BJ), the Research & Enterprise Office + the subject librarians on the following areas:
    • Metadata workflow and service development
    • Advocacy/training
    • Building a “Research Showcase”
    • CRIS-like development, bibliometrics, and supporting the REF
    • Developing staff profiles on the University’s website
    • E-theses
    • Helpdesk integration (…possibly)

The following are projects—part of the current Library I.T. strategy—that I’ll contribute to but probably won’t lead, and/or work that’s going on in the background that I need to stay abreast of:

  1. Reading list development (project);
  2. Authentication (project);
  3. Participation in various JISC working groups as well as UKCoRR and LISN;
  4. Working with the Acquisitions team on new team rôles/areas of work;
  5. Monitoring and guiding e-resource management (ERM), authentication, and responding to user problems (this area of work will be looked after day-to-day by the Library (E-resources) Assistant (EV), supported by other staff, as part of the cover for my JISC project work);
  6. Supporting the subject librarian for technology in a review of the Library’s presence on the University Portal;
  7. Supporting the subject librarians in promoting and supporting the use of RefWorks 2.0;
  8. Supporting the HELS in administering copyright/digitisation services and the use of Blackboard.
  9. Initiating a new CALM user group.
  10. Co-ordinating LIG (the Library Innovation Group).
  11. Participating in the work of LNCD.

G’won then: what have I forgotten about?

RSP CRIS event – Tuesday 22 July

Posted on August 3rd, 2011 by Paul Stainthorp

We apologise for the late arrival of this blog post.

On the 22nd of July I was at the University of Nottingham for an RSP (Repositories Support Project) event, Repositories and CRIS: working smartly together. A few of us from the UKCoRR committee were there, giving UKCoRR’s new Twitter account some hammer. My colleagues, David Young from the University Research Office and Elif Varol from the Library, also went.

Here are some very brief notes on the various presentations and activities – all of the slides are on the RSP’s website.

  • Simon Kerridge of ARMA (on the research administration, the CERIF standard, and the EXRI project). This has already led to some movement on the idea of a JISCMail ‘super list’ to allow information to be shared easily between members of ARMA and UKCoRR. All the talk of CERIF and REF requirements has also prompted us (Lincoln people) into action – a separate blog post about this will follow.
  • RePOSIT presentations and breakout discussion – this was great fun. Like being back at the RSP Winter School again. Repository work and advocacy makes far more sense and the panic easiest quelled when I talk to other repository managers around a table.
  • After lunch: more on euroCRIS from Mark Cox of King’s College London. Loads to look at, including the R4R (Readiness 4 REF) plugin for EPrints, and MICE (Measuring Impact under CERIF).
  • The University of Glasgow’s “alternative approach”, involving some hardcore use of EPrints. This is the model Lincoln is following and it’s great to see it working so successfully for Glasgow. See their Research Outcomes work and Will Nixon & colleagues’ Enlighten blog. Also related: EPrints: A Hybrid CRIS/Repository.
  • Finally, a whistlestop tour of EPrints version 3.3 and some of its new features, including one-click installation of plugins from the EPrints “Bazaar”. Looks very cool.

At this point: run for bus.

#blgk and #evolvingenglish

Posted on December 15th, 2010 by Paul Stainthorp

I’m blogging from the balcony of the Cotton Room, overlooking the atrium of the British Library at St Pancras. (I’ve been attending a meeting in London today, and to save money I booked two single, off-peak train tickets: leaving me with plenty of time to explore the BL.)

I’ve based myself here for the day because:

  1. The British Library is committed to making information of all kinds as widely available as possible.” Translation: good, reliable, free wifi FTW.
  2. I particularly wanted to visit the BL’s “Growing Knowledge: the evolution of research” exhibition (hashtag:#blgk), which is all about innovative tools for digital research. It’s worth a look (you don’t have to visit the smart, white digital exhibition suite at St Pancras; you can register online and explore many of the tools over the Web). There’s some good stuff here: some of the services and discussions could be useful additional material for our own ‘Working on the Web‘ staff workshops, and I’m particularly interested in the Research Information Centre (a still-in-development BL/Microsoft Research project to build a scientific VRE [Virtual Research Environment]): of obvious relevance to the University of Lincoln’s own VRE project work (more about which soon). Register/log in, and you can watch a video about the RIC. I also filled in their evaluation survey for Growing Knowledge.
  3. The other exhibition on at the moment is Evolving English; a trawl through the historical, social and cultural roots of the English language. It’s fantastic. If you’re at all interested in languages, and you’re in London before April 2011, you should go. I sat in a booth and recorded myself reading a Mr Tickle story, for their English dialect/accent map. (Hashtag:#evolvingenglish)

Working on the web (staff workshop)

Posted on November 12th, 2010 by Paul Stainthorp

This is another in the collection of staff workshops that I’m running with Joss Winn of CERD and David Young from the University Research Office. This one has its own wiki page on CERD’s Learning Lab site.

Working on the web: Learning to use new web technologies and tools for teaching and research

This session will provide an introduction to a variety of freely available web technologies and tools that can enrich research, teaching and learning.

This workshop aims to help academics make better use of the web in their teaching and research. In this hour-long session we will show you how free and easy-to-use web-based tools such as RSS, social bookmarking, blogs and wikis can support your teaching and your students’ learning. Follow up, more in-depth classroom-based support is available through the Centre for Educational Research and Development.

Staff from all disciplines are encouraged to attend

This workshop aims to help academics improve their research by making better use of the web

We aim to:

  • Learn about different ways that the web can support student collaboration
  • Improve the way you observe and assess contribution to group work
  • Understand new ways of communicating, supporting and engaging with your students
  • Prepare your students for new and emerging ways of working on the web
  • Understand the benefits and manage the risks of teaching and learning in public
  • Improve the way you search for funding information
  • Improve the way you receive and organise information about research and funding
  • Find out about ways to make research collaboration, networking and manuscript production with others more effective and efficient
  • Find out how to connect and find others with shared research interests

We’re running one workshop a month between now and May 2011. University of Lincoln staff can book a place via the Staff Learning & Development Portal site.