Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Implementing Durham Etheses - Sebastian Palucha (Pecha Kucha)


Published on

Pecha Kucha slides on Durham University's experience of implementing their Etheses system, presented by Sebastian Palucha, on Friday 2nd August 2013 at Repository Fringe 2013.

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

Implementing Durham Etheses - Sebastian Palucha (Pecha Kucha)

  1. 1. Implementing Durham E-Theses Presented by Sebastian Palucha #rfringe13 CC BY jitze
  2. 2. ∂ Durham E-Theses  Initial project spring/summer 2009  First deposit September 2009  ~ 300 research theses per year  Simple deposit, single PDF  EThOS interoperability  EPrints 3.1.3 (born 2009) CC BY didbygraham
  3. 3. ∂ Registered: EThOS, Driver, OCL Digital Gateway (2010 spr.) EThOS harvest in operation (2010 sum.) Google Analytics stats (2010 dec.) EThOS digitised theses loaded (2011 sum.) Google Custom Search (aut. 2011) Collaboration with The BL to improve EThOS services (aut. 2011 – spr. 2012) EU/ICO Cookie Law support (2013 sum.) local digitisation project, 10k (2012 spr2 – ) MySQL migrated to UTF-8 (2013 spring) Creative Common Licences introduced (2012 aut.) CC BY AlishaV Key milestones
  4. 4. ∂ Branding: uniform user experience • Issues: browsers, branding changes • Durham University CMS CSS • Eprints 3 CSS
  5. 5. ∂ Simplistic single PDF deposit • Details > Upload > Deposit • LDAP integration + user field population • Embargo implemented in first screen CC BY Pink Sherbet Photography
  6. 6. ∂ Cover pages  Highly customized LaTeX code  Issues with UTF-8 both LaTeX and plugin  Issues with dynamic if/else
  7. 7. ∂ Google Analytics: full text downloads • Two steps: 1. PDF download link (core code) 2. special GA profile • URL structure include department codes ?DDD32 • Internal code modification
  8. 8. ∂ EThOS interoperability through OAI-PMH harvest • Issues with out of the box plug-in, changes to XML schema needed • uketdterms:qualificationlevel not defined in EPrints data model • Embargo date not included. Plugin assumes embargo on an record level, whereas EP on an document level! • Added department names • Occasional issues with UTF-8 encoding
  9. 9. ∂ EThOS download WS • Script for mass download groovy EthosDownloadClient.groovy -i 238830 –m download
  10. 10. ∂ EThOS avoiding duplication • We store EThOS persistent IDs • We modified /cgi/oai2 script to conditionally exclude ethos records • Modified record can be exposed to EThOS harvest in future
  11. 11. ∂ UTF-8 issues Unknown copy/paste issues seen:  OAI/PMH  Cover Pages LaTeX  Abstract pages Solution:  Code modification  Whole MySQL database migration to UTF-8, fortunately double encoding CC BY familymwr
  12. 12. ∂ Creative Common Licences  Approached by student: specific query about particular CC to be used  A lot of redefinition is code
  13. 13. ∂ CC outreach
  14. 14. ∂ Better search, DRO integration Google Custom Search with modified search results
  15. 15. ∂ Retrospective digitisation project • 10k paper theses being digitised by local company • Mass upload with metadata in XML file and digitised material in PDF files, web and archive version. A lot of metadata and quality issues • Interesting samples of other materials: big prints, DVDs, CDs, cassette tapes, microfilms, small datasets and research software.
  16. 16. ∂ EU/ICO Cookies Law CC BY USAG-Humphreys 31687107@N07/6206906748
  17. 17. ∂ Repository versus real life • Users would like to deposit other than PDF files. • Requested “Dark” storage • Encrypted PDFs • Take down requests, and Web cached content. How far should we liaise with external world • Some students are not aware about consequences of web deposits: 3rd party copyright, sensitive data not embargoed etc. • Disciplinary differences; not only humanities vs. sciences. • External user requesting contact with author or supervisors
  18. 18. ∂ Sustainability • Operational: virtualization, operating systems support, database • Customization: Bespoken changes and technology deficit • Support: hard to coordinate across the University departments CC BY Rennett Stowe
  19. 19. ∂ Future plans  Review process, be paper free, include pass list, extend workflow to exam board  Actively encourage students to use CC licences by demonstrate its benefit  Encourage deposit of key data sets and explore data visualization  Migrate to new repository framework  Integration with Durham University RIS  Google Analytics live stats, integration with IRUS-UK CC BY Boston Public Library
  20. 20. ∂ Repository of the future CC by CC BY Keoni Cabral