DORSDL 2006

1. DORSDL 2006 The repository as a general university administrative system A case story and practical example

2. Introduction • PURE at 9 universities + hospitals et al • PURE is an J2EE enterprise application • Holistic approach to research productions • Data gathering, Storing, Converting, Exchanging, Exhibiting, Publishing, Reporting • De-centralized gathering • Business model

3. PURE as an Institutional Repository • PURE compared to IRs • Automated, rights-managed electronic publishing of bibliographical and bibliometrical meta-data and publication full-text files. EP is achieved in two ways: • Two web-services • PUREportal framework • More about this later

4. PURE as an Institutional Repository • Tool for ingestion and access • PURE is a tool for batch ingestion and conversion and for management of large data collections. • PURE is a tool for creating technical access to data - not only over web services: • OAI-PMH with Dublin Core + SVEP + DDF-MXD • XML I/O generic • .PXA (PURE XML Archive format) meta-data + relations + binaries

5. PURE as a general university admin sys • Tool for planning and managing data gathering work processes • Involving large groups of users and introducing GUI issues. • Workflow and the role-based distribution of user tasks. • "The ambition was to create a system so easy to use, that researchers will register their own activity and publications and use the PURE system as a daily tool in their research work rutines". • easy-to-use tool for routinely submitting research • Fast-track onto personal and project-specific websites and into the Google indexes

6. PURE as a general university admin sys • Central solution for advanced statistics and reporting: • about research publications, projects, research funding, and other types of research activities. • university directors and administrators with instant and updated information on the research of their university and allows them to implement incentive structures that improve dissemination of the research of the university.

7. The history of joint development • Initiated at Aalborg University Library • Now purchased by 9 universities (DK + SE) plus a number of other research institutions and hospitals. • A central piece in the research administration and dissemination efforts of most of the Danish universities • The core of emerging Current Research Information Systems for these institutions.

8. The history of joint development • The PURE board • representatives from each university + the private development company. • Decides on all important development steps and coordinates shared financing of development work. • The incentive to participate in the shared planning and financing of further developments has been strong enough to secure a large part of the development tasks as common priorities.

9. The history of joint development • A commercial product • PURE is not Open Source. • The PURE board is a user group like SMUG, SFX and Metalib User Group • The process has been characterized by strong commitment to a common development process. • The PURE project and the development process has also been partly financed by the Danish National Electronic Research Library programme • PURE is now fully financed by the participating universities.

10. The history of joint development • The joint development tactics • The modus operandi was not to develop a product. Instead, the chain of events was to: • First identify the demands at all the participating research institutions. • Then to collectively agree on a definition. • Next to plan sub-consequent data conversions or changes to work processes at one or more of the participating institutions. • Finally to start designing, developing and testing. • Compliant with modern-day software development methodologies such as Extreme Programming or Agile Software Development • Leaving traditional commercial development, where focus is at "market demands".

11. The history of joint development • Advantages to each institution • Access to a highly qualified forum, in which ideas and challenges can be discussed • Developing and sharing standards, features and best practises • Using and influencing a standardized meta-data model • Organizational processes are becoming identical across research institutions • The academic productions are homogeneously measurable across institutions • Low risk on development projects • Low cost for custom development of new features

12. The history of joint development • Roles of the software vendor • System architecture and data model architecture • Usability and GUI • Programming, testing and quality assurance • Versioning and documentation • Release management • Implementations including data conversion and local systems' integration • Education of local superusers, IT-staffs and web programmers • 2nd level support • Error reporting and feature request management • User group meetings

13. The history of joint development • Meta-data model • Any meta-data model can be implemented in PURE • Frameworks exist for the purpose of implementing any meta-data model based solely on local demands. • PURE also comes with a ready-made standard meta-data model • The process of joint development lead to the PURE-MDM, which is used collectively by all universities. • Changes to the meta-data model: • A research institution suggest changes or additions. They are discussed and all institutions agree on a shared, common definition of the suggested changes. Atira A/S then puts forward a development and implementation budget, which then is approved by the PURE board. • Nationalization + Availability

14. More about PURE • Data gathering • De-centralized data submission from the entire academic body. • Individual roles • User-rights per researcher • Adaptive browser-interface • Built-in help and local vocabulary • Data submission can be tied into an automated work-flow • Enables peer-validation of submitted data to ensure quality and completion.

15. More about PURE • Key words • Central keywords hierarchy can be defined by system administrators. • Unlimited in levels • Researchers can add their own keywords at the lowest • Keywords from this central hierarchy can be added to all content types in the meta-data model: Persons, Projects, Organisations, Publications, etc. • Keywords allows users to browse the entire academic production hierarchically by keywords • "The combination of a fixed library-originated keyword hierarchy and unrestricted researcher-originated keywords have proven to solve both a number of internal challenges and and to offer very efficient means of increasing the availability of the research production - particularly to the public (non-academic) users."

16. More about PURE • Dynamic integration • To systems such as personnel systems, financial packages, administrative and technical systems: LDAP, Active Directories, SSO and access/security systems • Such source-systems must feed several PURE content types: • Persons (and their roles) • Projects • Organisations and News feeds. • In many cases, user authentication must be build on dynamic integration. • PURE offers a technical framework with a plug-in architecture for customizing integration to such sources.

17. More about PURE • Data import • Methodical, controlled and validated import of historical data: The PURE XML Archive (PXA) format • Converting data from any given source to PXA can involve more or less manual work, depending on the source data. So rationalize this work, a number of standard converters are currently being build; for data from PubMed, among others.

18. More about PURE • Data storage • Meta-data • Customer-definable SQL environment, Hibernate O/R mapping layer • Binary objects • Just stored in the file system, DOI, etc. • DSpace and FEDORA • Ready-made PURE-connectors to DSpace and FEDORA has been developed, thus facilitating rich binary storage to LTP systems in a lean way

19. More about PURE • Data exhibition • Web services • RPC/encoded and Document/Literal, each with a rich library of methods • E.g. APA, VANCOUVER, HARVARD and others • Code example in the paper

20. More about PURE • Data exhibition • OAI • Meta-data harvesting over the OAI-PMH protocol as a Data provider • Dublin Core, SVEP, DDF-MXD • PURE dev. framework for adding more formats under OAI-PMH • Z39.50 • Searches from library system • Generic XML I/O • A generic XML I/O unit allows for data represented in XML to imported and exported • Format exports • Search results as PDF/RFT (Harvard, Vancouver, MLA, APA, etc.), XML, Reference Manager

21. Modules and the ASP-model • Modules • PURE basic module, Reports, Bibliometry, Student theses, Press, External publications • ASP model • License-free hosted service • For smaller research institution, an ASP service was recently made available, making PURE available with the full feature set in each module from EUR 4.000 per year.

22. Modules and the ASP-model • Reporting • Ready-made reports for listing and calculating data in PURE • Each report can be customized • new custom reports can be defined (GUIO) • Similar set exits for bibliometrical reporting and statistics

23. Modules and the ASP-model • Bibliometry • Various citation types and journal impact factors can be added • Manual task (GUI) • Import from ISI and Scopus is currently being investigated

24. Modules and the ASP-model • Student theses • Same as publications but with different users and different validation

25. Modules and the ASP-model • Press • Adding data from XML-based feeds from news agencies to publications, organizations and other content types in PURE

26. Modules and the ASP-model • External publications • Import of previous work of the researchers • Allowing research from current job position + past research from other workplaces • Allows researchers to maintain a complete CV. Data can be entered manually or imported from compatible systems.

27. DORSDL 2006 Http://pure.atira.dk Powerpoint, full paper, contact info Http://vbn.dk Example of PURE-based research portal