New Task Group CRIS Architecture & Development Maximilian Stempfhuber RWTH Aachen University Library

Agenda A view to research information The role of CERIF As a data model In the CRIS development process Why a new Task Group? Task Group’s Mission

Information & Research Process Work programm Project proposal Project Results Transfer Wealth creation Research organisations Research programmes Research strategy State of the Art Proposal Management Project management (Human)Resources Infrastructure Experiments Publication management Communication Research data Software Prizes, patents Expertise Commercial products Knowledge Wealth Excellence Research Information

CRIS Semantic & Temporal Aspects Project Org. Unit Funding Programme Person Expertise CV Results Publications Events Software Patents Current Research Information System

CERIF A Data Model for CRIS Common European Research Information Format Equipment Project Organisation Service FundingProgramme Patent Skills CV Product Event Person Classification ( Semantics ) Classification ( Semantics ) Publication

CERIF A Data Model for CRIS Common European Research Information Format Entity Relationship Model Generators for several DBMS CERIF-XML as exchange format Code of Good Practice Commercial software systems Proprietary implementations

Same Model… … different results

Current Process Code of Good Practice Organizational view Covers whole process Waterfall-like Missing Aspects (Software) Architecture Technology Reference Implementation

Looking Beyond… … the CRIS domain Administrative systems at the institution Local information systems (OAR etc.) Community systems (ResearchGate etc.) Clusters of Excellence (Idea League) Virtual Organizations (Fraunhofer, Helmholtz, Leibniz, Max-Planck)

CERIF-CRIS Connectivity CERIF-CRIS Projects, Persons, Org. Units, Publications, Events, Research Programmes, etc. CERIF-CRIS Projects, Persons, Org. Units, Publications, Events, Research Programmes, etc. CERIF-CRIS Projects, Persons, Org. Units, Publications, Events, Research Programmes, etc. CERIF-XML Institutional Repository Research Data Repository FinanceHuman Resources Project Management

Community CRIS

euroCRIS Strategy euroCRIS Enhance existing CRIS Fill gaps with new CRIS Connect CRIS with a common CERIF wrapper Create standardized, reusable services

The Gap… CERIF Concrete System Code of Good Practice high low Agreements, Standards, Best Practices, Re-Use … between model and implementation

What’s Missing? Operating System Database Management System CERIF Data Access Layer Business Logic User Interface CERIF- XML Search, Harvesting, ServicesCode of Good Practice

Why is it important? 20 CERIF : 80 Development & Testing

What can be gained… … for euroCRIS as an organization? Community building Exchange Reuse Evolution Spreading ideas & Connectivity … beyond CERIF

What can be gained… … for euroCRIS members? Using building blocks Reducing development & testing Getting additional functionality Opening ones system & content … even in combination with commercial software

Requirements Requirements engineering (Functional) Software specification Code of Good Practice (Updated) Best Practice Examples / DRIS (Updated) Available (commercial) solutions

Database Systems Paradigms (Relational, Object-Oriented, XML, multi-dimensional DBMS) Systems (IBM DB2, Oracle, PostgreSQL; commercial vs. Open Source) Interfaces (ODBC, JDBC, Perl DBI, PEAR) Query languages (SQL, OQL, XQuery) Schema evolution / migration

Database Abstraction Separating software architecture from the (physical) database model Encapsulation vs. normalization Object-Relational-Mapping (ORM) Schema evolution / migration Convention over configuration (Coding by convention) & tool support

Programming & Managing Re-use of modules and libraries Generating CRIS Open Source code base Share experience with colleagues – Scalability (e.g. middleware) – Reliability (e.g. components) – Integrated Development Environments (IDE) – Development process (SCRUM, V-Model, MDA, …)

Software Architecture Permanent evolution vs. re-use – Development philosophy → architecture – Domain modeling → architecture – Software frameworks → architecture – Tools support → architecture – Programming languages → architecture Current buzz words: SOA/REST, Cloud Computing, RIA, BPM, Portal/CMS

Functional Modules Self containment Standardized interfaces Standardized functionality Standardized input (e.g. CERIF-XML) Standardized output? CRIS plug-in architecture needed

Workflow Business Process Modeling (BPM) Workflows at the UI level Quality assurance in CRIS Event/data-driven services Drives re-usable software modules (e.g. input verification, data acquisition) & processes

User Interface Common / consistent user experience Re-use of interaction patterns Sharing solutions (e.g. CSS frameworks) Sharing knowledge (e.g. accessibility) Integration CRISs and services

Information Design Common ways for expressing – Semantic relationships – Temporal aspects – Qualities & quantities Software modules for visualizations – Network graphs – Timelines – Charts, … Experiences with commercial software

Statistics & Reporting Defining recurring information needs Standardizing on basic data formats Statistics / reporting as a (re-usable / commercial) service Software modules Layout templates (e.g. XSLT, XML FO)

External Access Defining public CRIS services – Functional specification – Interface specification – I/O format specification Services – Searching for entities – Data analysis / information extraction

Data Exchange Harvesting interfaces Entity extraction Replication Federation Schema mapping

TG Roadmap Establishing TG Mission Recruiting TG Members Initial Survey: Where are we now? Where are we going? – Technologies used (DMBS, languages etc.) – Methodologies used (SOA, SCRUM, outsourcing etc.) – Gap analysis: Topics for support & exchange, common modeling of CRIS architectures, abstraction layers, module specifications etc.