The ARROW Project: A consortial institutional repository solution, combining Open Source and proprietary software  David G...
Outline <ul><li>Why did we want a repository? </li></ul><ul><li>What  is ARROW? </li></ul><ul><li>What is VITAL and how do...
Why did we want a repository? <ul><ul><li>provides a platform for promoting research output in the ARROW context </li></ul...
What is ARROW? <ul><li>ARROW Project:  </li></ul><ul><ul><li>Originally funded for 3 years until December 31, 2006, recent...
Who is ARROW? <ul><li>Founding ARROW Partners: </li></ul><ul><ul><li>Monash University (lead institution) </li></ul></ul><...
What did the ARROW project set out to achieve? <ul><ul><li>Solution for storing any digital output </li></ul></ul><ul><ul>...
What did the ARROW project set out to achieve? (2) <ul><ul><li>Meeting DEST reporting requirements </li></ul></ul><ul><ul>...
What is ARROW now? <ul><ul><li>A development project </li></ul></ul><ul><ul><li>Combining Open Source and proprietary soft...
Why Fedora? <ul><li>ARROW wanted:  </li></ul><ul><ul><li>a robust, well architected underlying platform </li></ul></ul><ul...
ARROW and Fedora ™ <ul><li>Since the beginning of the project ARROW has worked actively and closely with Fedora ™ and the ...
Partnering for success, support  and survivability <ul><li>ARROW needed to partner with a developer who could not only pro...
What is VITAL? <ul><li>ARROW specified software created and fully supported by VTLS Inc. built on top of Fedora ™  that cu...
VITAL architecture overview Fedora ™ Indexes Handles server Web services Google exposure SRU/SRW Batch Loading Tool Access...
Where are we now? 2004 <ul><ul><li>Developed architecture </li></ul></ul><ul><ul><li>Selected, tested Fedora ™  OJS </li><...
ARROW Repositories <ul><li>Monash University </li></ul><ul><ul><li>http://arrowprod.lib.monash.edu.au:8000/access </li></u...
Implementation decisions <ul><li>Atomistic or compound objects? </li></ul><ul><li>Descriptive metadata </li></ul><ul><ul><...
Policy frameworks and decisions <ul><li>Direct or mediated deposit? </li></ul><ul><ul><ul><li>managing workflows </li></ul...
External searching and harvesting <ul><li>Realised need to develop a discovery service for Australian institutional reposi...
ARROW Discovery Service <ul><li>http://search.arrow.edu.au/ </li></ul><ul><li>Provides a national resource discovery servi...
Open Source contributions for Fedora <ul><li>Already made: </li></ul><ul><ul><li>SRU/SRW </li></ul></ul><ul><ul><li>HANDLE...
<ul><li>Upcoming VITAL Version 3.0 </li></ul><ul><ul><li>Authentication/Authorization Services. </li></ul></ul><ul><ul><ul...
What have we learnt so far? <ul><li>Multiple partners are good: </li></ul><ul><ul><li>Sharing of information and experienc...
What have we learnt so far? (2) <ul><li>That there aren’t enough real standards in this area </li></ul><ul><li>Open versus...
ARROW Stage 2 <ul><li>Funded to the end of 2007 </li></ul><ul><li>Supporting the RQF </li></ul><ul><li>Creative developmen...
Some changes in direction <ul><li>Trying to do more development ourselves to: </li></ul><ul><ul><li>Spread the knowledge <...
Supporting the RQF <ul><li>Inclusion of all discrete pieces of evidence, regardless of content type </li></ul><ul><ul><li>...
Creative development of ARROW institutional repositories <ul><li>Inclusion of multimedia and creative works produced in Au...
ARROW Projects <ul><li>ARROW is planning a number of local projects targeting local and community needs. These will intera...
Partner projects in 2007 <ul><li>Gathering research output from websites (UNSW) </li></ul><ul><li>Displaying outputs throu...
Supporting Australian engagement with institutional repositories <ul><li>FRODO and MERRI projects have resulted in a signi...
The ARROW community <ul><li>Sharing knowledge and experiences </li></ul><ul><li>Annual meeting – inaugural one September 8...
Building partnerships to further enhance repositories <ul><li>Through partnerships with other projects ARROW will endeavor...
PILIN -   Persistent Identifiers and Linking INfrastructure <ul><li>Growing realisation that sustainable identifier infras...
Questions? <ul><li>ARROW Project </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>http://arrow.edu.au/   <...
Upcoming SlideShare
Loading in …5
×

dorsdl2006-arrow

1,100 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,100
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

dorsdl2006-arrow

  1. 1. The ARROW Project: A consortial institutional repository solution, combining Open Source and proprietary software David Groenewegen ARROW Project Manager
  2. 2. Outline <ul><li>Why did we want a repository? </li></ul><ul><li>What is ARROW? </li></ul><ul><li>What is VITAL and how does it relate to Fedora? </li></ul><ul><li>Where is ARROW now? </li></ul><ul><li>What have we learnt so far? </li></ul><ul><li>ARROW Stage-2 </li></ul>
  3. 3. Why did we want a repository? <ul><ul><li>provides a platform for promoting research output in the ARROW context </li></ul></ul><ul><ul><li>safeguards digital information </li></ul></ul><ul><ul><li>gathers an institution’s research output into one place </li></ul></ul><ul><ul><li>provides consistent ways of finding similar objects </li></ul></ul><ul><ul><li>allows information to be preserved over the long term </li></ul></ul><ul><ul><li>allows information from many repositories to be gathered and searched in one step </li></ul></ul><ul><ul><li>enables resources to be shared, while respecting access constraints (when software allows access controls) </li></ul></ul><ul><ul><li>enables effective communication and collaboration between researchers </li></ul></ul>
  4. 4. What is ARROW? <ul><li>ARROW Project: </li></ul><ul><ul><li>Originally funded for 3 years until December 31, 2006, recently extended for 12 months. </li></ul></ul><ul><ul><li>Funded by the Australian Commonwealth Department of Education, Science and Training (DEST), under the Research Information Infrastructure Framework for Australian Higher Education. </li></ul></ul><ul><li>“ The ARROW project will identify and test software or solutions to support best practice institutional digital repositories comprising e-prints, digital theses and electronic publishing.” </li></ul>
  5. 5. Who is ARROW? <ul><li>Founding ARROW Partners: </li></ul><ul><ul><li>Monash University (lead institution) </li></ul></ul><ul><ul><li>National Library of Australia </li></ul></ul><ul><ul><li>The University of New South Wales </li></ul></ul><ul><ul><li>Swinburne University of Technology. </li></ul></ul><ul><li>ARROW Members: </li></ul><ul><ul><li>University of South Australia </li></ul></ul><ul><ul><li>University of Southern Queensland </li></ul></ul><ul><ul><li>Queensland University of Technology </li></ul></ul><ul><ul><li>Central Queensland University </li></ul></ul><ul><ul><li>University of Western Sydney </li></ul></ul><ul><ul><li>La Trobe University </li></ul></ul><ul><ul><li>4 other RUBRIC members are expected to sign soon </li></ul></ul><ul><li>Together they form the ARROW Community </li></ul>
  6. 6. What did the ARROW project set out to achieve? <ul><ul><li>Solution for storing any digital output </li></ul></ul><ul><ul><ul><li>Initial focus on print equivalents – theses, journal articles </li></ul></ul></ul><ul><ul><ul><li>Now looking at other datasets, learning objects </li></ul></ul></ul><ul><ul><li>More than just Open Access – some things need to be restricted </li></ul></ul><ul><ul><ul><li>Copyright </li></ul></ul></ul><ul><ul><ul><li>Confidentiality/ethical considerations </li></ul></ul></ul><ul><ul><ul><li>Work in progress </li></ul></ul></ul>
  7. 7. What did the ARROW project set out to achieve? (2) <ul><ul><li>Meeting DEST reporting requirements </li></ul></ul><ul><ul><ul><li>Expected move to Research Quality Framework (RQF) has increased the focus on repositories </li></ul></ul></ul><ul><ul><li>Employ Open Standards </li></ul></ul><ul><ul><ul><li>Making sure the data is transferable in the future </li></ul></ul></ul><ul><ul><li>Deliver Open Source Tools back to the FEDORA Community </li></ul></ul><ul><ul><li>Solution that could offer on-going technical support and development past the end of the funding period </li></ul></ul>
  8. 8. What is ARROW now? <ul><ul><li>A development project </li></ul></ul><ul><ul><li>Combining Open Source and proprietary software: </li></ul></ul><ul><ul><ul><li>Fedora ™ </li></ul></ul></ul><ul><ul><ul><li>VITAL </li></ul></ul></ul><ul><ul><ul><li>Open Journal Services (OJS) </li></ul></ul></ul><ul><ul><li>NOT a centralised or hosting solution </li></ul></ul><ul><ul><ul><li>Every member has their own hardware and software </li></ul></ul></ul>
  9. 9. Why Fedora? <ul><li>ARROW wanted: </li></ul><ul><ul><li>a robust, well architected underlying platform </li></ul></ul><ul><ul><li>a flexible object-oriented data model </li></ul></ul><ul><ul><li>to be able to have persistent identifiers down to the level of individual datastreams, accommodating its compound content model </li></ul></ul><ul><ul><li>to be able to version both content and disseminators (think of software behaviours for content) </li></ul></ul><ul><ul><li>clean and open exposure of APIs with well-documented SOAP/REST web services. </li></ul></ul>
  10. 10. ARROW and Fedora ™ <ul><li>Since the beginning of the project ARROW has worked actively and closely with Fedora ™ and the Fedora Community </li></ul><ul><ul><li>ARROW Project Technical Architect is a member of Fedora Advisory Board </li></ul></ul><ul><ul><li>ARROW Project Technical Architect sits on Fedora Development Group </li></ul></ul><ul><ul><li>This is reinforced by VTLS Inc. </li></ul></ul><ul><ul><li>VTLS President is a member of Fedora Advisory Board </li></ul></ul><ul><ul><li>VITAL Lead Developer sits on Fedora Development Group </li></ul></ul>
  11. 11. Partnering for success, support and survivability <ul><li>ARROW needed to partner with a developer who could not only produce the software but could provide ongoing user support and development after December 31, 2006 </li></ul><ul><li>Why VTLS Inc.? </li></ul><ul><ul><li>VTLS wanted to be a development partner </li></ul></ul><ul><ul><li>Had begun work on a repository solution already </li></ul></ul><ul><ul><li>Familiar with library sector </li></ul></ul><ul><ul><li>Willing to produce a combination of a proprietary solution, Fedora and other Open Source software </li></ul></ul>
  12. 12. What is VITAL? <ul><li>ARROW specified software created and fully supported by VTLS Inc. built on top of Fedora ™ that currently provides: </li></ul><ul><ul><li>VITAL Manager </li></ul></ul><ul><ul><li>VITAL Portal </li></ul></ul><ul><ul><li>VITAL Access Portal </li></ul></ul><ul><ul><li>VALET - Web Self-Submission Tool </li></ul></ul><ul><ul><li>Batch Loader Tool </li></ul></ul><ul><ul><li>Handles Server (CNRI) </li></ul></ul><ul><ul><li>Google Indexing and Exposure </li></ul></ul><ul><ul><li>SRU / SRW Support </li></ul></ul>
  13. 13. VITAL architecture overview Fedora ™ Indexes Handles server Web services Google exposure SRU/SRW Batch Loading Tool Access Portal Valet Vital Manager
  14. 14. Where are we now? 2004 <ul><ul><li>Developed architecture </li></ul></ul><ul><ul><li>Selected, tested Fedora ™ OJS </li></ul></ul><ul><ul><li>VITAL 1.0 </li></ul></ul>2005 <ul><ul><li>VITAL 1.3 </li></ul></ul><ul><ul><li>Started populating repositories </li></ul></ul><ul><ul><li>OAI-PMH harvesting </li></ul></ul><ul><ul><li>ARROW Discovery Service </li></ul></ul><ul><ul><li>Open sources tools released </li></ul></ul><ul><ul><li>VITAL 2.0 </li></ul></ul>2006 <ul><ul><li>VITAL 2.1 </li></ul></ul><ul><ul><li>VITAL 3.0 (in test) </li></ul></ul><ul><ul><li>Authentication/Authorization Services </li></ul></ul><ul><ul><li>Enhanced Content Models </li></ul></ul><ul><ul><li>Usage and access statistics </li></ul></ul><ul><ul><li>User configurable interfaces </li></ul></ul><ul><ul><li>Movement towards a pure Web based interface </li></ul></ul><ul><ul><li>Support for OAI sets </li></ul></ul><ul><ul><li>Integration with 3rd party modules like federated search </li></ul></ul>2007 ARROW Stage-2
  15. 15. ARROW Repositories <ul><li>Monash University </li></ul><ul><ul><li>http://arrowprod.lib.monash.edu.au:8000/access </li></ul></ul><ul><li>University of New South Wales </li></ul><ul><ul><li>http://arrow.unsw.edu.au/ </li></ul></ul><ul><li>Swinburne University of Technology </li></ul><ul><ul><li>http://researchbank.swinburne.edu.au/access/ </li></ul></ul><ul><li>Central Queensland University </li></ul><ul><ul><li>http://library-resources.cqu.edu.au:8888/access/ </li></ul></ul>
  16. 16. Implementation decisions <ul><li>Atomistic or compound objects? </li></ul><ul><li>Descriptive metadata </li></ul><ul><ul><ul><li>adopt one or enjoy MANY types? </li></ul></ul></ul><ul><ul><ul><li>JHOVE validation </li></ul></ul></ul><ul><ul><ul><li>JHOVE metadata extraction </li></ul></ul></ul><ul><li>Use cases and content modelling </li></ul><ul><li>What import /export formats? </li></ul><ul><ul><ul><li>honouring what standards? </li></ul></ul></ul><ul><ul><ul><li>validation, when and how? </li></ul></ul></ul>
  17. 17. Policy frameworks and decisions <ul><li>Direct or mediated deposit? </li></ul><ul><ul><ul><li>managing workflows </li></ul></ul></ul><ul><li>Open or closed access? </li></ul><ul><ul><ul><li>LDAP authentication? </li></ul></ul></ul><ul><ul><ul><li>XACML authorisation </li></ul></ul></ul><ul><ul><ul><ul><li>creating policies -who can do what? </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Shibboleth </li></ul></ul></ul></ul><ul><li>Persistent URL format? </li></ul><ul><li>External searching and harvesting? </li></ul><ul><ul><ul><li>OAI-PMH </li></ul></ul></ul><ul><ul><ul><li>spidering </li></ul></ul></ul><ul><li>post ARROW project support </li></ul><ul><li>For more detail see Andrew Treloar’s talk at: http://www.lib.virginia.edu/digital/fedoraconf/schedule.shtml </li></ul>
  18. 18. External searching and harvesting <ul><li>Realised need to develop a discovery service for Australian institutional repositories </li></ul><ul><ul><li>The ARROW Discovery Service developed by the NLA, provides consolidated searching across many Australian repositories, (uses OAI-PMH) </li></ul></ul><ul><ul><li>Picture Australia developed by the NLA, harvesting image collections (uses AOI-PMH) </li></ul></ul><ul><ul><li>SRU/SRW interface released as Open Source Software </li></ul></ul><ul><li>Harvesting </li></ul><ul><ul><li>Google and other service providers </li></ul></ul>
  19. 19. ARROW Discovery Service <ul><li>http://search.arrow.edu.au/ </li></ul><ul><li>Provides a national resource discovery service including: </li></ul><ul><ul><li>providing an appropriate search interface </li></ul></ul><ul><ul><ul><li>simple search, advanced search, & browse options </li></ul></ul></ul><ul><ul><li>contributing to other networks </li></ul></ul><ul><ul><ul><li>OAIster, Yahoo, Google </li></ul></ul></ul><ul><ul><li>Ensuring appropriate local institutional and national “branding” of the service </li></ul></ul><ul><ul><ul><li>occurs throughout the ADS interface and the exchanged metadata </li></ul></ul></ul><ul><ul><li>providing appropriate subject-based access </li></ul></ul><ul><ul><ul><li>The Australian Standard Research Classification list </li></ul></ul></ul>
  20. 20. Open Source contributions for Fedora <ul><li>Already made: </li></ul><ul><ul><li>SRU/SRW </li></ul></ul><ul><ul><li>HANDLES </li></ul></ul><ul><ul><li>JHOVE Metadata extraction </li></ul></ul><ul><ul><li>Exposure to Web indexing crawlers. </li></ul></ul><ul><li>Coming in 2006: </li></ul><ul><ul><li>LDAP Authentication </li></ul></ul><ul><ul><li>Administrative Reporting </li></ul></ul><ul><ul><li>Bulk Citation Export </li></ul></ul><ul><ul><li>Statistics for Public Users </li></ul></ul><ul><ul><li>Metadata Synchronisation Requirements </li></ul></ul>
  21. 21. <ul><li>Upcoming VITAL Version 3.0 </li></ul><ul><ul><li>Authentication/Authorization Services. </li></ul></ul><ul><ul><ul><li>XACML (Policy enforcement) </li></ul></ul></ul><ul><ul><li>Enhanced Content Models. </li></ul></ul><ul><ul><li>Usage and access statistics. </li></ul></ul><ul><ul><li>User configurable interfaces. </li></ul></ul><ul><ul><li>Movement towards a pure Web based interface. </li></ul></ul><ul><ul><li>Support for OAI sets. </li></ul></ul><ul><ul><li>Integration with 3rd party modules like federated search. </li></ul></ul><ul><ul><li>Access to content via VTLS reseller arrangements. </li></ul></ul>Future of VITAL
  22. 22. What have we learnt so far? <ul><li>Multiple partners are good: </li></ul><ul><ul><li>Sharing of information and experiences </li></ul></ul><ul><ul><li>Sharing of development work </li></ul></ul><ul><ul><li>Multiple perspectives on issues </li></ul></ul><ul><li>and bad: </li></ul><ul><ul><li>Multiple perspectives on issues </li></ul></ul><ul><ul><li>Scope creep </li></ul></ul><ul><ul><li>Managing expectations </li></ul></ul><ul><ul><li>Pressure on the project management team </li></ul></ul><ul><ul><li>Pressure on development team and partners </li></ul></ul><ul><ul><li>Deadline conflicts </li></ul></ul><ul><li>Software development feels slow, both commercial and open source </li></ul><ul><li>Development with a commercial partner can be tricky </li></ul>
  23. 23. What have we learnt so far? (2) <ul><li>That there aren’t enough real standards in this area </li></ul><ul><li>Open versus closed repositories, or information management versus accessibility is a BIG ISSUE </li></ul><ul><li>Repositories are only partly about software - advocacy, policy, institutional engagement and grunt work need equal attention </li></ul><ul><li>Constraints of dealing with copyright </li></ul>
  24. 24. ARROW Stage 2 <ul><li>Funded to the end of 2007 </li></ul><ul><li>Supporting the RQF </li></ul><ul><li>Creative development of institutional repositories </li></ul><ul><li>Supporting Australian engagement with institutional repositories </li></ul><ul><li>Building partnerships to further enhance repositories </li></ul><ul><li>Identifier Management Infrastructure for e-Research Resources (PILIN) </li></ul>
  25. 25. Some changes in direction <ul><li>Trying to do more development ourselves to: </li></ul><ul><ul><li>Spread the knowledge </li></ul></ul><ul><ul><li>Leverage our use of Fedora </li></ul></ul><ul><li>Want to work with VTLS in new ways </li></ul><ul><ul><li>Contract is finished now </li></ul></ul><ul><ul><li>Some work we need to do is too local for VTLS </li></ul></ul><ul><ul><li>VINES </li></ul></ul>
  26. 26. Supporting the RQF <ul><li>Inclusion of all discrete pieces of evidence, regardless of content type </li></ul><ul><ul><li>Including traditional text evidence and less traditional evidence, such as art works and music compositions or performances </li></ul></ul><ul><li>Provision for maximum possible exposure of content </li></ul><ul><ul><li>Subject to copyright constraints. </li></ul></ul><ul><li>Inclusion of metadata and links to content in commercial resources. </li></ul><ul><li>Reporting to DEST through multiple channels </li></ul><ul><ul><li>Such as Research Master, or direct to the repository. </li></ul></ul><ul><li>Support for access and authorisation regimes. </li></ul><ul><li>Retention of all evidence </li></ul><ul><ul><li>To build institutional research profiles over time. </li></ul></ul>
  27. 27. Creative development of ARROW institutional repositories <ul><li>Inclusion of multimedia and creative works produced in Australian universities. </li></ul><ul><ul><li>To date have had limited exposure nationally or internationally. </li></ul></ul><ul><li>Addition of annotation capability </li></ul><ul><li>Inclusion of datasets and other research output not easily provided in any other publishing channel. </li></ul><ul><ul><li>In conjunction with the DART (ARCHER) Project. </li></ul></ul><ul><li>Exploration of the research-teaching nexus by facilitating multiple uses of content held in repositories. </li></ul><ul><li>Integration with or development of new tools that will allow value added services for repositories. </li></ul><ul><ul><li>For instance the creation of e-portfolios or CVs of research output of individual academics . </li></ul></ul>
  28. 28. ARROW Projects <ul><li>ARROW is planning a number of local projects targeting local and community needs. These will interact directly with Fedora ™ and VITAL where appropriate. The development is being done within the ARROW Community. </li></ul>
  29. 29. Partner projects in 2007 <ul><li>Gathering research output from websites (UNSW) </li></ul><ul><li>Displaying outputs through websites (portfolios) (UNSW/Swinburne) </li></ul><ul><li>Understanding workflows and needs of academics (UNSW/Swinburne) </li></ul><ul><li>Improving the ARROW Discovery Service (NLA) </li></ul><ul><ul><li>OAI Sets support </li></ul></ul><ul><ul><li>Greater automation </li></ul></ul><ul><ul><li>Statistics capture and reporting </li></ul></ul><ul><ul><li>Integration of e-journals </li></ul></ul><ul><li>Usability analysis (Swinburne) </li></ul><ul><li>Data needs survey (Swinburne) </li></ul><ul><li>Building Rules for Access to Controlled Electronic Resources (BRACER) (Monash) </li></ul>
  30. 30. Supporting Australian engagement with institutional repositories <ul><li>FRODO and MERRI projects have resulted in a significant leap in the levels of understanding and engagement with repositories in Australia, </li></ul><ul><li>Now the challenge is to translate this into substantial repository activity. </li></ul><ul><li>The newly formed ARROW Community is intended to provide a central platform for support and the exchange of information . </li></ul>
  31. 31. The ARROW community <ul><li>Sharing knowledge and experiences </li></ul><ul><li>Annual meeting – inaugural one September 8, 2006 </li></ul><ul><li>Regular workshops </li></ul><ul><li>Working Groups </li></ul><ul><ul><li>ARROW Repository Managers Group </li></ul></ul><ul><ul><li>ARROW Development Group </li></ul></ul><ul><li>Possibly groups for: </li></ul><ul><ul><li>Portfolio design </li></ul></ul><ul><ul><li>Metadata: METS, MODS, DC and the future </li></ul></ul><ul><li>Discussion group </li></ul><ul><ul><li>GoogleGroup </li></ul></ul><ul><li>ARROW provides logistical and admin support </li></ul>
  32. 32. Building partnerships to further enhance repositories <ul><li>Through partnerships with other projects ARROW will endeavor to use best practice and new innovations to further enhance Australian repositories beyond their current limitations. </li></ul><ul><li>These include: </li></ul><ul><ul><li>APSR: http://www.apsr.edu.au/ </li></ul></ul><ul><ul><li>DART/ARCHER: http:// www.dart.edu.au / </li></ul></ul><ul><ul><li>ICE: http://ice.usq.edu.au/ </li></ul></ul><ul><ul><li>MAMS: http://www.melcoe.mq.edu.au/projects/MAMS/ </li></ul></ul><ul><ul><li>OAK-Law: http://www.oaklaw.qut.edu.au/ </li></ul></ul><ul><ul><li>RUBRIC: http://www.rubric.edu.au/ </li></ul></ul>
  33. 33. PILIN - Persistent Identifiers and Linking INfrastructure <ul><li>Growing realisation that sustainable identifier infrastructure is required to deal with the vast amount of digital assets being produced and stored within universities. </li></ul><ul><li>This is a particular challenge for e-research communities where massive amounts of data are being generated without any means of managing this data over any length of time. </li></ul><ul><li>The broad objectives are to: </li></ul><ul><ul><li>Support adoption and use of persistent identifiers and shared persistent identifier management services by the project stakeholders. </li></ul></ul><ul><ul><li>Plan for a sustainable, shared identifier management infrastructure that enables persistence of identifiers and associated services over archival lengths of time. </li></ul></ul>
  34. 34. Questions? <ul><li>ARROW Project </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>http://arrow.edu.au/ </li></ul></ul><ul><li>ARROW Project Manager </li></ul><ul><ul><li>[email_address] </li></ul></ul>

×