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.
@ulcc www.ulcc.ac.uk
EPrints User Group
The meeting will begin at 10.30am on Tuesday 13th January 2015
#EPrintsUG
@ulcc www.ulcc.ac.uk
Welcome & Matters from previous meeting
http://bit.ly/EPrintsUG130115
#EPrintsUG
@ulcc www.ulcc.ac.uk
Open Access Update
Valerie McCutcheon
#EPrintsUG
Valerie McCutcheon, Research Information Manager
End-to-End
Open Access (OA) Process Review and
Improvements
#e2eoa
http:/...
Research Information Systems
Student
System
Research Mapping
System & Web Pages
Research
System
Enlighten -
Institutional
...
Popular Process –
Low Barrier for Authors
• Email details of every paper accepted for publication to:
research-openaccess@...
REPOSITORY
SPREADSHEET
LIBRARY SERIALS
SYSTEM
FINANCE SYSTEM
PUBLISHERS
@Acceptance
date?
INTERMEDIARY
SERVICE
/
RCUK
REF
...
3500003285 618.35
3500003285 184.82
3500003285 251.69
3500003285 401.44
2520000360 1258.47
MDPI
Luminescent Measurement Sy...
System specific + generic usability
E2E Project Planned Outputs
Case Studies – Open Access
• OA Issues and Potential Solution
• Embedding future REF
requirement
• Advocacy
• Outcomes and Sustainability
E2E Project...
Metadata specification
Improve OA reporting
Improve award linkage functionality
E2E Project Planned Outputs
RCUK
REF
HORIZ...
– 'CASRAIfying’ – standard definitions
and generic technical specification
Consortia Advancing Standards in Research Admin...
@ulcc www.ulcc.ac.uk
CASRAI
David Baker
#EPrintsUG
Sustainable Interoperability:
Local, National, International
CASRAI & EPrints
Use Case: REF Submission Prep
As an institution preparing for a REF
submission we need to ensure that those of our
publica...
Use Case: APC Intake
As a funder collecting reports from funded
institutions our evaluation unit needs
information on expe...
Why CASRAI?
● Lack of interoperability a root cause of admin
burden and assessment blindness
● Need a sustainable agreemen...
To be interoperable...
“...one should be actively engaged in the
ongoing process of ensuring that the systems,
procedures ...
What is CASRAI?
● nonprofit global network of organizations
● projects commissioned to develop common
reusable agreements ...
Common Interop Patterns
● A - B Interop
o information stored with one database needs to get
into another database (so a lo...
Applied to Open Access Interop
● Article submission (A - B)
● CRIS/Repository (A - B)
● APC reporting (A - B)
● OA Policy ...
CASRAI-UK Open Access Group
● Glasgow (Chair)
● ESPRC (Chair)
● Jisc (Sponsor)
● MRC
● NERC
● Wellcome Trust
● HEFCE
23
● ...
CASRAI-UK Open Access Profile
● Output Metadata
o (ID; title; authors; version; etc)
● Access Metadata
o (license type; fr...
CASRAI-UK OA Interop Use Cases
● REF Post-2014 (A - B)
● APC Intake (A - B)
● Horizon 2020 (A - B)
● Internal Institutiona...
Next Steps
● Finalize the policy view of the OA Data
Profile
● Create the technology view
● Public review/comment
● Implem...
Thank-you
info@casrai.org
@ulcc www.ulcc.ac.uk
RIOXX
Sheridan Brown & Timothy Miles-Board
#EPrintsUG
rioxx…in 5 minutes
Sheridan Brown
rioxx project consultant
Key Perspectives Ltd.
Who is involved?
• Developed for:
• Funded by:
• Developed by: Paul Walk, Sheridan Brown
• Public consultation: V4OA proje...
What is rioxx?
An application profile
… a set of metadata elements and
guidelines
Note: applies solely to publications
What is rioxx for?
the specific purpose of enabling
funders to monitor compliance
with their Open Access policies
Metadata elements
21 metadata elements
10 mandatory
5 recommended
6 optional
Mandatory elements
1. dc:identifier
a persistent identifier for the resource (http uri)
2. dc:language
3. dc:source
e.g. I...
6. rioxxterms:author
the use of an ORCID is recommended
7. rioxxterms:project
funder_name
recorded as text, and/or
funder_...
8. rioxxterms:type
a controlled list of resource types is provided
9. rioxxterms:version
uses recommendations from NISO/AL...
10. ali:license_ref
• Specified by National Information Standards
Organisation (NISO)
• http URI points to a license
• Lic...
Help!
Jisc has funded an
EPrints plugin for rioxx
Jisc is funding technical support for the plugin:
EPrints Services (host...
@ulcc www.ulcc.ac.uk
Developing a Data Repository
Stephen Grace, David McElroy, Rory McNicholl and
Timothy Miles-Board
#EP...
Developing a Data Repository
Stephen Grace and David McElroy, UEL
Rory McNicholl and Timothy Miles-Board, ULCC
EPrints Use...
Developing a Data Repository
1. Developing data.uel
2. Demos
– CoinDOI
– Repository Links
3. Look and Feel
“Research organ...
Developing data.uel
• Rationale
• Functional Specifications
• Mock-ups
• Metadata Schemas
• Relational Diagrams
Rationale
• UEL adopted RDM policy March 2012
– Library & Learning Services (LLS) will create
a register of datasets…
– [a...
Functional Specifications
• Excel spreadsheets describing:
– What we wanted
– Why we wanted it
– Who was responsible for d...
Functional Specifications
Description of what we think we
need
Our reasoning for this. By including this
we were able to t...
Mock-ups
• Clear indication of
what we want
• Red numbers refer
to spreadsheet detail
Mock-ups
• Spreadsheet linked to the Mock-up
wireframes
• Full descriptions with HTML
Metadata Schemas
• Based on ReCollect and Datacite
• Only mandatory Datacite fields are
mandatory in data.uel
“Research or...
Metadata Schemas
Relational Diagrams
• How projects
can be linked
to data
collections
• Potentially to
each other
over time
Demos
– CoinDOI
– Repository Links
Look & Feel
• Developed in-house at UEL
– (with help from ULCC of course)
• Important to make the repositories feel like
p...
Thank you
UEL:
Stephen Grace
http://orcid.org/0000-0001-8874-2671
s.grace@uel.ac.uk
@StephenGraceful
David McElroy
http://...
@ulcc www.ulcc.ac.uk
The future of EPrints Integration
Arkivum
#EPrintsUG
We’ll store your data for 25 years*,
100% guaranteed data safety
* Longer is OK too!
Contents
• Arkivum in 60 secs
• Current EPrints integration
• Improvements and next steps
Arkivum in 60 seconds
SLA with 100% data
integrity guaranteed
World-wide professional
indemnity insurance
Long term contra...
Example Customers
Data Archiving - Integrations
21 October 2014 60
Eprints: data deposit
EPrints
Arkivum
Appliance
Review Approve
Appliance Cache
ArkivumService
Researcher
Editor
FilesFiles...
EPrints: automatic archiving
21 October 2014 62
EPrints: archive status
21 October 2014 63
Chain of custody
• Checksums to confirm correct transfers
• Lock-down the content
• Confirmation of replication
• Update m...
Eprints: data access
EPrints
Arkivum
Appliance
Review Approve
Appliance Cache
ArkivumService
Researcher
Editor
Files
ready...
EPrints: request access
21 October 2014 66
EPrints: approve request
21 October 2014 67
EPrints: automated restore
21 October 2014 68
EPrints: download file
21 October 2014 69
Access workflow
• Immediate access to small files
• Review/approve/notify for large files
• Simple expectation of retrieva...
Access control done by EPrints
• Open access: no license, no barriers
• Unrestricted use, but request for access
• Unrestr...
Limitations of current approach
• All data goes through EPrints
• Can’t link to data already in the archive
• Can’t push d...
Direct data deposit into Arkivum
EPrints
Arkivum
Appliance
Review
Approve
Deposit file
Appliance Cache
ArkivumService
Rese...
Automated uploader
EPrints
Arkivum
Appliance
Review Approve
Files
Appliance Cache
ArkivumService
Researcher
Editor
Check D...
Work to be done
• Seamless experience for the user
• Security model
• Permissions: who can deposit, link, approve
• Effici...
JISC Research Data Spring
Questions?
Plugin
http://bazaar.eprints.org/378/
Documentation
http://files.eprints.org/978/1/ArkivumEPrintsPlugin21V11A.p...
@ulcc www.ulcc.ac.uk
It’s EPrints, but not as you
know it…
Timothy Miles-Board & David McElroy
#EPrintsUG
virtual
:-)
flexibility
:-|
dcterms:dateAccepted
published
submitted
completed
rioxxterms:project
projects
funders
<rioxxterms:project funder_name=“EPSRC”>
JA/139K/02
</rioxxterms:project>
<rioxxterms:project funder_name=“NERC”>
GLX_456_...
admin
only
github.com
/eprintsug
/rioxx2
@ulcc www.ulcc.ac.uk
Introduction and
Community Future
Adam Field
#EPrintsUG
Community Engagement Lead
• Understand and Promote Community
Priorities
• Support Community Interactivity,
Productivity an...
How can I help?
Response Number of Responders
Documentation IIIIIIII
Better Communication III
Roadmap III
New Features / M...
Documentation
• Documentation means many things to many
people
• Community based activity – Everyone can
contribute
• Lots...
Better Communication
• New role (Community Engagement Lead)
– Email: af05v@ecs.soton.ac.uk
– Telephone: 023 8059 8814
– Tw...
EPrints 3.3.13
EPrints 4
EPrints 3.4
EPrints 3.3.14
EPrints Roadmap
January 13th, 2015
EPrints User Group Meeting
EPrints Development Roadmap
Roadmap
Milestone Date
EPrints 3.3.13 January 2015
EPrints 3.3.14 Early 2015
EPrints 3.4 Easter 2015
EPrints 4 End of 2015
EPrints 3.3.13
• Released January 8th, 2015
• Minor release
– 150 Commits
– 88 files changed
• General Stability and Secur...
EPrints 3.3.14
• To be released early 2015
• Minor Release
– Stability Improvements
• New Bazaar Features
– Channels and B...
EPrints 3.4.0
• Coming around Easter 2015
• Response to a more diverse repository
landscape
• Stepping Stone towards EPrin...
EPrints 4 / 3.4.0 Key Philosophy
• “Base” EPrints storing and handling of generic
data and objects
• “Layers” to handle sp...
3.4 Releases
• Collections of metadata schemas, renderers,
plugins and packages tested together for a
specific purpose (th...
Base
Publications
MetadataSchema
IRUSTracker
PublicationsRouter
ORCIDSupport
WOK/Scopus
Projects/Funder&Rioxx2
IRStats2
EP...
Base
Education
MetadataSchema
MePrints
Bookmarks
Collections
EdShareStyleUser
Interface
EPrints 3.4 for Open Education
Base
ResearchData
MetadataSchema
ReCollect
DataCite
Arkivum
ExemplarSimple
StoragePlugin
EPrints 3.4 for Open Research Dat...
EPrints for Micro Repositories
Base
BespokeDataset
Importer
Renderer
@ulcc www.ulcc.ac.uk
Lunch
Resume at 13:30
#EPrintsUG
@ulcc www.ulcc.ac.uk
User Access Control
John Salter/John Beaman
#EPrintsUG
EPrints User Access Control
Also know as: -
EPrints Access Control Layer
(ACL)
John Salter & John Beaman
Introduction
• We have spent some time trying to write an Access
Control system for EPrints
• It’s been a horror!
• One of...
Out of the box User Access Control
• EPrints (you all know what this is, right..?) has basic
control at the document level...
Requirements
• Control access to Eprints, Documents
• Control access based on:
– User attributes (e.g. signed-in via Shibb...
EPACL: EPrints Access Control Layer
• Modular Design
– Doesn't overwrite any existing 'security' specified on documents.
–...
ACL Objects
• ACL Authority
– Corresponds to a method of authentication (e.g. Shibboleth, LDAP etc.)
• ACL Role
– Authoris...
Request vs User
• Two basic steps to authorise access - request and user
• First EPrints checks if the request has appropr...
Dealing with rejection
• What happens when someone is denied access?
–Document landing pages
–Restricted summary pages
–Co...
Summary Page citation style
• How do we deal with rejected requests (i.e. what do we
show)?
• We can define different cita...
Document-level landing pages
• Partly born out of DOI requirements
• Individual documents may have their own DOI, so ideal...
The horrors (and the solutions)
• The out-of-the-box document security is deep within
EPrints (we learnt about doing some ...
The horrors (and the solutions) [continued…]
• All sorts of crazy inheritance complexities
• EPrints doesn't use 'sessions...
Screenshot – Manage records
Screenshot – Manage ACL Roles
Screenshot – Edit ACL Roles
Screenshot – Manage ACL Groups
Screenshot – Edit ACL Groups
Screenshot – Edit Item
Screenshot – Example Item (no ACL)
Screenshot – Example Item (ACL restricted)
Screenshot – Example Document landing page
Thank you for listening!
• These presentation notes and other ACL documentation
can be found on the EPrints wiki at
http:/...
@ulcc www.ulcc.ac.uk
Discussion Groups
#EPrintsUG
@ulcc www.ulcc.ac.uk
Tea Break
Resume at 15:05
#EPrintsUG
@ulcc www.ulcc.ac.uk
Discussion Groups
#EPrintsUG
@ulcc www.ulcc.ac.uk
Development Wishlist
#EPrintsUG
@ulcc www.ulcc.ac.uk
Open Discussion
#EPrintsUG
@ulcc www.ulcc.ac.uk
Close
#EPrintsUG
EPrints User Group January 2015
EPrints User Group January 2015
EPrints User Group January 2015
EPrints User Group January 2015
EPrints User Group January 2015
EPrints User Group January 2015
EPrints User Group January 2015
EPrints User Group January 2015
Upcoming SlideShare
Loading in …5
×

EPrints User Group January 2015

972 views

Published on

We are pleased to announce that in collaboration with the University of East London (UEL), we hosted the EPrints UK User Group on Tuesday 13th January 2015 in Senate House.

Published in: Software
  • Be the first to comment

  • Be the first to like this

EPrints User Group January 2015

  1. 1. @ulcc www.ulcc.ac.uk EPrints User Group The meeting will begin at 10.30am on Tuesday 13th January 2015 #EPrintsUG
  2. 2. @ulcc www.ulcc.ac.uk Welcome & Matters from previous meeting http://bit.ly/EPrintsUG130115 #EPrintsUG
  3. 3. @ulcc www.ulcc.ac.uk Open Access Update Valerie McCutcheon #EPrintsUG
  4. 4. Valerie McCutcheon, Research Information Manager End-to-End Open Access (OA) Process Review and Improvements #e2eoa http://e2eoa.org/ oagoodpractice@jiscmail.ac.uk http://openaccess.jiscinvolve.org/wp/pathfinder-projects/
  5. 5. Research Information Systems Student System Research Mapping System & Web Pages Research System Enlighten - Institutional Repository Finance System Human Resources System PROJECT OUTPUTS • Publications • Datasets • Artwork • Exhibitions • Impact (soon) ALL REVIEWED BY LIBRARY STAFF Smug dissatisfaction?
  6. 6. Popular Process – Low Barrier for Authors • Email details of every paper accepted for publication to: research-openaccess@glasgow.ac.uk and attach the accepted final version • Library open access team checks funder details, what a publication allows, whether payment is required. We do the admin if we can – pay invoices, enter date into our repository.
  7. 7. REPOSITORY SPREADSHEET LIBRARY SERIALS SYSTEM FINANCE SYSTEM PUBLISHERS @Acceptance date? INTERMEDIARY SERVICE / RCUK REF HORIZON 2020 LOCAL INFO
  8. 8. 3500003285 618.35 3500003285 184.82 3500003285 251.69 3500003285 401.44 2520000360 1258.47 MDPI Luminescent Measurement Systems for the Investigation of a Scramjet Inlet-Isolator Sensors One Publication – Many Transactions
  9. 9. System specific + generic usability E2E Project Planned Outputs Case Studies – Open Access
  10. 10. • OA Issues and Potential Solution • Embedding future REF requirement • Advocacy • Outcomes and Sustainability E2E Project Planned Outputs – Workshops
  11. 11. Metadata specification Improve OA reporting Improve award linkage functionality E2E Project Planned Outputs RCUK REF HORIZON 2020 LOCAL INFO Not all organisations have Funder’s Reference Linked to Publications in their Repository
  12. 12. – 'CASRAIfying’ – standard definitions and generic technical specification Consortia Advancing Standards in Research Administration Information UK – Many inputs REF, RCUK/RIOXX, Horizon 2020, Charities Open Access Fund, Jisc (Meeting 16th Jan 2015), Institutional Requirements….. – Community build - avoid replication PURE, EPrints, Hydra, Symplectic, Converis, ARMA, SCONUL, SCURL, RLUK, UKCoRR, COAR, CCC, Jisc initiatives…. MetadataCASRAI Standard
  13. 13. @ulcc www.ulcc.ac.uk CASRAI David Baker #EPrintsUG
  14. 14. Sustainable Interoperability: Local, National, International CASRAI & EPrints
  15. 15. Use Case: REF Submission Prep As an institution preparing for a REF submission we need to ensure that those of our publications which are in-scope for REF OA policy meet the repository deposit deadline requirements so that we can remove any remaining compliance gaps before submitting. 16
  16. 16. Use Case: APC Intake As a funder collecting reports from funded institutions our evaluation unit needs information on expenditure of funds related to OA article-processing-charges so that we can effectively monitor our OA policy. 17
  17. 17. Why CASRAI? ● Lack of interoperability a root cause of admin burden and assessment blindness ● Need a sustainable agreement mechanism ● Avoid forcing agreement at the wrong layer 18
  18. 18. To be interoperable... “...one should be actively engaged in the ongoing process of ensuring that the systems, procedures and culture of an organisation are managed in such a way as to maximise opportunities for exchange and reuse of information, whether internally or externally.” Paul Miller UKOLN/Jisc (2000) 19
  19. 19. What is CASRAI? ● nonprofit global network of organizations ● projects commissioned to develop common reusable agreements for interoperability ● institutions, funders, vendors, libraries 20
  20. 20. Common Interop Patterns ● A - B Interop o information stored with one database needs to get into another database (so a local step can occur) ● A + B Interop o information in multiple databases needs to be aggregated (so analysis can occur) ● Coarse-grained or Fine-grained Interop o bulk reports or detailed queries 21
  21. 21. Applied to Open Access Interop ● Article submission (A - B) ● CRIS/Repository (A - B) ● APC reporting (A - B) ● OA Policy Monitoring (A + B) ● Others? 22
  22. 22. CASRAI-UK Open Access Group ● Glasgow (Chair) ● ESPRC (Chair) ● Jisc (Sponsor) ● MRC ● NERC ● Wellcome Trust ● HEFCE 23 ● St. Andrews ● Kings ● Edinburgh ● Elsevier ● Eprints (new)
  23. 23. CASRAI-UK Open Access Profile ● Output Metadata o (ID; title; authors; version; etc) ● Access Metadata o (license type; freedoms; embargos) ● Compliance Metadat o (first/subsequent deposits; checks) ● Financing Metadat o (funder; APC; EU component; etc) 24
  24. 24. CASRAI-UK OA Interop Use Cases ● REF Post-2014 (A - B) ● APC Intake (A - B) ● Horizon 2020 (A - B) ● Internal Institutional Workflows ● Others?? 25
  25. 25. Next Steps ● Finalize the policy view of the OA Data Profile ● Create the technology view ● Public review/comment ● Implementation pilots / phase 2 work 26
  26. 26. Thank-you info@casrai.org
  27. 27. @ulcc www.ulcc.ac.uk RIOXX Sheridan Brown & Timothy Miles-Board #EPrintsUG
  28. 28. rioxx…in 5 minutes Sheridan Brown rioxx project consultant Key Perspectives Ltd.
  29. 29. Who is involved? • Developed for: • Funded by: • Developed by: Paul Walk, Sheridan Brown • Public consultation: V4OA project; rioxx website
  30. 30. What is rioxx? An application profile … a set of metadata elements and guidelines Note: applies solely to publications
  31. 31. What is rioxx for? the specific purpose of enabling funders to monitor compliance with their Open Access policies
  32. 32. Metadata elements 21 metadata elements 10 mandatory 5 recommended 6 optional
  33. 33. Mandatory elements 1. dc:identifier a persistent identifier for the resource (http uri) 2. dc:language 3. dc:source e.g. ISSN or ISBN for the electronic resource 4. dc:title 5. dcterms:dateAccepted the date on which the resource was accepted for publication
  34. 34. 6. rioxxterms:author the use of an ORCID is recommended 7. rioxxterms:project funder_name recorded as text, and/or funder_id recommend using FundRef DOI or ISNI an alphanumeric identifier for the project must be recorded
  35. 35. 8. rioxxterms:type a controlled list of resource types is provided 9. rioxxterms:version uses recommendations from NISO/ALPSP Journal Article Versions Technical Working Group, e.g. Accepted Manuscript (AM), Version of Record (VoR)
  36. 36. 10. ali:license_ref • Specified by National Information Standards Organisation (NISO) • http URI points to a license • License has a start_date • Multiple licenses may apply, allowing for expression of embargos • If license is unknown, default position is “all rights reserved” <ali:license_ref start_date=“2015-02-17”>http:// creativecommons.org/licenses/by/4.0</ali.license_ref>
  37. 37. Help! Jisc has funded an EPrints plugin for rioxx Jisc is funding technical support for the plugin: EPrints Services (hosted repositories) ULCC (hosted repositories) Peter West (non-hosted repositories)
  38. 38. @ulcc www.ulcc.ac.uk Developing a Data Repository Stephen Grace, David McElroy, Rory McNicholl and Timothy Miles-Board #EPrintsUG
  39. 39. Developing a Data Repository Stephen Grace and David McElroy, UEL Rory McNicholl and Timothy Miles-Board, ULCC EPrints User Group, Senate House London, 13 January 2015 ULCC and UEL
  40. 40. Developing a Data Repository 1. Developing data.uel 2. Demos – CoinDOI – Repository Links 3. Look and Feel “Research organisations will ensure that EPSRC-funded research data is securely preserved for a minimum of 10 years…” (EPSRC, Expectation VII)
  41. 41. Developing data.uel • Rationale • Functional Specifications • Mock-ups • Metadata Schemas • Relational Diagrams
  42. 42. Rationale • UEL adopted RDM policy March 2012 – Library & Learning Services (LLS) will create a register of datasets… – [and] a portal for datasets which are suitable for sharing • Separate to ROAR – Different workflows – Not everything will be Open Access
  43. 43. Functional Specifications • Excel spreadsheets describing: – What we wanted – Why we wanted it – Who was responsible for doing it
  44. 44. Functional Specifications Description of what we think we need Our reasoning for this. By including this we were able to take advantage of our developers knowledge. If there is a better way of doing something they let us know. Some aspects of development were shared. Above we were to provide the metadata profile
  45. 45. Mock-ups • Clear indication of what we want • Red numbers refer to spreadsheet detail
  46. 46. Mock-ups • Spreadsheet linked to the Mock-up wireframes • Full descriptions with HTML
  47. 47. Metadata Schemas • Based on ReCollect and Datacite • Only mandatory Datacite fields are mandatory in data.uel “Research organisations will ensure that appropriately structured metadata describing the research data they hold is published and made freely accessible on the internet…” (EPSRC, Expectation V)
  48. 48. Metadata Schemas
  49. 49. Relational Diagrams • How projects can be linked to data collections • Potentially to each other over time
  50. 50. Demos – CoinDOI – Repository Links
  51. 51. Look & Feel • Developed in-house at UEL – (with help from ULCC of course) • Important to make the repositories feel like part of UEL – Branding (More later) – Single Sign On!
  52. 52. Thank you UEL: Stephen Grace http://orcid.org/0000-0001-8874-2671 s.grace@uel.ac.uk @StephenGraceful David McElroy http://orcid.org/0000-0002-0966-8862 d.mcelroy@uel.ac.uk @davidlmcelroy Research Data Services at UEL Repo data.uel.ac.uk Web www.uel.ac.uk/researchdata/ Blog datamanagementuel.wordpress.com ULCC: Rory McNicholl rory.mcnicholl@ulcc.ac.uk @RoryMcN Timothy Miles-Board timothy.miles-board@ulcc.ac.uk @drtjmb
  53. 53. @ulcc www.ulcc.ac.uk The future of EPrints Integration Arkivum #EPrintsUG
  54. 54. We’ll store your data for 25 years*, 100% guaranteed data safety * Longer is OK too!
  55. 55. Contents • Arkivum in 60 secs • Current EPrints integration • Improvements and next steps
  56. 56. Arkivum in 60 seconds SLA with 100% data integrity guaranteed World-wide professional indemnity insurance Long term contracts for enterprise data archiving Fully automated and managed solution Audited and certified to ISO27001 Data escrow, exit plan, no lock-in
  57. 57. Example Customers
  58. 58. Data Archiving - Integrations 21 October 2014 60
  59. 59. Eprints: data deposit EPrints Arkivum Appliance Review Approve Appliance Cache ArkivumService Researcher Editor FilesFiles Metadata Files Files safe Files safe Clear cache Clear cache EPrints StorageResearcher files Files safe Delete originals
  60. 60. EPrints: automatic archiving 21 October 2014 62
  61. 61. EPrints: archive status 21 October 2014 63
  62. 62. Chain of custody • Checksums to confirm correct transfers • Lock-down the content • Confirmation of replication • Update metadata and audit trail • Remove local copy (if desired)
  63. 63. Eprints: data access EPrints Arkivum Appliance Review Approve Appliance Cache ArkivumService Researcher Editor Files ready Request data Files Files Researcher files Wait Retrieve files Files ready Files
  64. 64. EPrints: request access 21 October 2014 66
  65. 65. EPrints: approve request 21 October 2014 67
  66. 66. EPrints: automated restore 21 October 2014 68
  67. 67. EPrints: download file 21 October 2014 69
  68. 68. Access workflow • Immediate access to small files • Review/approve/notify for large files • Simple expectation of retrieval time • Caching of files for repeated access
  69. 69. Access control done by EPrints • Open access: no license, no barriers • Unrestricted use, but request for access • Unrestricted use, but charge for access • Restricted use: request/approve access • Embargoed: no access for set period • Locked down: no access
  70. 70. Limitations of current approach • All data goes through EPrints • Can’t link to data already in the archive • Can’t push data to publication platforms • Can’t grant direct access to the archive
  71. 71. Direct data deposit into Arkivum EPrints Arkivum Appliance Review Approve Deposit file Appliance Cache ArkivumService Researcher Editor Add URL Get URL Retrieve File Check Data
  72. 72. Automated uploader EPrints Arkivum Appliance Review Approve Files Appliance Cache ArkivumService Researcher Editor Check Data Uploader Metadata URL Prepare dataset Local storage
  73. 73. Work to be done • Seamless experience for the user • Security model • Permissions: who can deposit, link, approve • Efficient and reliable transfer of big files • Relationship to SWORD • Timestamps, UUIDs, thumbnails, indexing • Quality control, sign-off
  74. 74. JISC Research Data Spring
  75. 75. Questions? Plugin http://bazaar.eprints.org/378/ Documentation http://files.eprints.org/978/1/ArkivumEPrintsPlugin21V11A.pdf Wiki Page http://wiki.eprints.org/w/Files/Configuration_and_User_Guide_for_version_ 2.1_of_the_EPrints/Arkivum_storage_plugin
  76. 76. @ulcc www.ulcc.ac.uk It’s EPrints, but not as you know it… Timothy Miles-Board & David McElroy #EPrintsUG
  77. 77. virtual
  78. 78. :-)
  79. 79. flexibility
  80. 80. :-|
  81. 81. dcterms:dateAccepted
  82. 82. published submitted completed
  83. 83. rioxxterms:project
  84. 84. projects funders
  85. 85. <rioxxterms:project funder_name=“EPSRC”> JA/139K/02 </rioxxterms:project> <rioxxterms:project funder_name=“NERC”> GLX_456_P </rioxxterms:project> <rioxxterms:project funder_name=“NERC”> JP/894Y/77 </rioxxterms:project>
  86. 86. admin only
  87. 87. github.com /eprintsug /rioxx2
  88. 88. @ulcc www.ulcc.ac.uk Introduction and Community Future Adam Field #EPrintsUG
  89. 89. Community Engagement Lead • Understand and Promote Community Priorities • Support Community Interactivity, Productivity and Outputs • Manage EPrints Services’ interactions and engagement with the community
  90. 90. How can I help? Response Number of Responders Documentation IIIIIIII Better Communication III Roadmap III New Features / More Development II Training Materials / Webinars I Developer Meets I Capturing Community Needs I Define and Strengthen Community I Better Web Site I
  91. 91. Documentation • Documentation means many things to many people • Community based activity – Everyone can contribute • Lots of ideas how to move forwards on this • Lets have a discussion session this afternoon
  92. 92. Better Communication • New role (Community Engagement Lead) – Email: af05v@ecs.soton.ac.uk – Telephone: 023 8059 8814 – Twitter: @gobfrey • Nascent Comms Strategy – Website Relaunch (early 2015) – UK User Group Google Group – Social Media and Mailing List – Webinars
  93. 93. EPrints 3.3.13 EPrints 4 EPrints 3.4 EPrints 3.3.14 EPrints Roadmap
  94. 94. January 13th, 2015 EPrints User Group Meeting EPrints Development Roadmap
  95. 95. Roadmap Milestone Date EPrints 3.3.13 January 2015 EPrints 3.3.14 Early 2015 EPrints 3.4 Easter 2015 EPrints 4 End of 2015
  96. 96. EPrints 3.3.13 • Released January 8th, 2015 • Minor release – 150 Commits – 88 files changed • General Stability and Security Improvements • Improvements to – DOI handling, Multilingual support, Search Indexing, Embargo Handling, Filetypes, Metatdata Normalisation, Abstract Page Rendering, CC Licenses, Subject Trees, Database Layer, Unicode Ordering, reCAPCHA, Audio Handling, OAI Exports, RSS, EndNote Imports, ISI Imports, List Rendering, EPScript, LaTeX handling, Automated Tests, Apache 2.4 Support
  97. 97. EPrints 3.3.14 • To be released early 2015 • Minor Release – Stability Improvements • New Bazaar Features – Channels and Badges – Assigned Wiki Pages for Documentation • Xapian Faceted Search by default
  98. 98. EPrints 3.4.0 • Coming around Easter 2015 • Response to a more diverse repository landscape • Stepping Stone towards EPrints 4.0
  99. 99. EPrints 4 / 3.4.0 Key Philosophy • “Base” EPrints storing and handling of generic data and objects • “Layers” to handle specific metadata schema, import/export, rendering, search, etc. for specific domains
  100. 100. 3.4 Releases • Collections of metadata schemas, renderers, plugins and packages tested together for a specific purpose (the pizza model) • Initial Releases for: – Open Access Publications – Open Education – Open Data
  101. 101. Base Publications MetadataSchema IRUSTracker PublicationsRouter ORCIDSupport WOK/Scopus Projects/Funder&Rioxx2 IRStats2 EPrints 3.4 for Publications
  102. 102. Base Education MetadataSchema MePrints Bookmarks Collections EdShareStyleUser Interface EPrints 3.4 for Open Education
  103. 103. Base ResearchData MetadataSchema ReCollect DataCite Arkivum ExemplarSimple StoragePlugin EPrints 3.4 for Open Research Data LargeFileUpload Mechanisms
  104. 104. EPrints for Micro Repositories Base BespokeDataset Importer Renderer
  105. 105. @ulcc www.ulcc.ac.uk Lunch Resume at 13:30 #EPrintsUG
  106. 106. @ulcc www.ulcc.ac.uk User Access Control John Salter/John Beaman #EPrintsUG
  107. 107. EPrints User Access Control Also know as: - EPrints Access Control Layer (ACL) John Salter & John Beaman
  108. 108. Introduction • We have spent some time trying to write an Access Control system for EPrints • It’s been a horror! • One of our use-cases is for Research Data, but it could be used on other repository types
  109. 109. Out of the box User Access Control • EPrints (you all know what this is, right..?) has basic control at the document level - the 'security' field: – ‘public’ (Open Access) – ‘validuser’ (anyone who's got an account on that EPrints instance) – ‘staffonly’ (Repository editors/admins) • This doesn't cover the requirements for some repositories...
  110. 110. Requirements • Control access to Eprints, Documents • Control access based on: – User attributes (e.g. signed-in via Shibboleth) – Location / IP address (e.g. on-campus) • Simple interface to assign restrictions
  111. 111. EPACL: EPrints Access Control Layer • Modular Design – Doesn't overwrite any existing 'security' specified on documents. – Will be available as a standard EPrints Plugin (EPM package) via the EPrints Bazaar – ACL Authority modules governing different methods of Authentication (see later) can be developed separately – These modules can simply be 'dropped in' to the existing framework as required
  112. 112. ACL Objects • ACL Authority – Corresponds to a method of authentication (e.g. Shibboleth, LDAP etc.) • ACL Role – Authorised by an ACL Authority with zero or more 'filters' applied – Filters act as additional requirements (e.g. ACL_Authority='LDAP', Filter='dc=leeds.ac.uk') • ACL Group – Each ACL Group consists of one or more ACL Roles – The ACL Roles are combined within an ACL Group by being 'OR'ed or 'AND'ed together – One or more ACL Groups are applied to EPrints data objects (e.g. eprints, documents) – The ACL Groups applied to EPrints data objects are 'OR'ed or 'AND'ed together
  113. 113. Request vs User • Two basic steps to authorise access - request and user • First EPrints checks if the request has appropriate access rights • If so, any additional user requirements are also checked • If not, the request is denied (since the user's credentials are irrelevant at that point)
  114. 114. Dealing with rejection • What happens when someone is denied access? –Document landing pages –Restricted summary pages –Contact details to request access?
  115. 115. Summary Page citation style • How do we deal with rejected requests (i.e. what do we show)? • We can define different citation styles depending on whether the request is allowed or denied • 'Restricted' citations may be required (e.g. to satisfy the minimum metadata requirements of a DOI)
  116. 116. Document-level landing pages • Partly born out of DOI requirements • Individual documents may have their own DOI, so ideally need their own ‘landing page’ • Document landing pages should contain at least the mandatory metadata fields if linked from a DOI
  117. 117. The horrors (and the solutions) • The out-of-the-box document security is deep within EPrints (we learnt about doing some really cranky Perl-fu) • Documents don't use the SummaryPage - again this is deep in the code (we learnt lots about Eprints Triggers) • Apache 2.2 and 2.4 differ in the way they handle IP addresses (Seb did some patching of EPrints code - but this hasn't been released - may be in 3.3.13?)
  118. 118. The horrors (and the solutions) [continued…] • All sorts of crazy inheritance complexities • EPrints doesn't use 'sessions' in the same way as most other web software. Sessions are only created when a user logs in (we think user accounts need to be automatically created - is this right? It would be useful for tracking re-use) • EPrints documentation is *ahem* offering room for improvement */ahem*...
  119. 119. Screenshot – Manage records
  120. 120. Screenshot – Manage ACL Roles
  121. 121. Screenshot – Edit ACL Roles
  122. 122. Screenshot – Manage ACL Groups
  123. 123. Screenshot – Edit ACL Groups
  124. 124. Screenshot – Edit Item
  125. 125. Screenshot – Example Item (no ACL)
  126. 126. Screenshot – Example Item (ACL restricted)
  127. 127. Screenshot – Example Document landing page
  128. 128. Thank you for listening! • These presentation notes and other ACL documentation can be found on the EPrints wiki at http://wiki.eprints.org/w/EPrints_User_Group_2015-01-13 • Our contact details: j.beaman@leeds.ac.uk j.salter@leeds.ac.uk • Any questions?
  129. 129. @ulcc www.ulcc.ac.uk Discussion Groups #EPrintsUG
  130. 130. @ulcc www.ulcc.ac.uk Tea Break Resume at 15:05 #EPrintsUG
  131. 131. @ulcc www.ulcc.ac.uk Discussion Groups #EPrintsUG
  132. 132. @ulcc www.ulcc.ac.uk Development Wishlist #EPrintsUG
  133. 133. @ulcc www.ulcc.ac.uk Open Discussion #EPrintsUG
  134. 134. @ulcc www.ulcc.ac.uk Close #EPrintsUG

×