1 / 30

New Task Group CRIS Architecture & Development

New Task Group CRIS Architecture & Development. Maximilian Stempfhuber RWTH Aachen University Library stempfhuber@bth.rwth-aachen.de. 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.

aure
Télécharger la présentation

New Task Group CRIS Architecture & Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New Task GroupCRIS Architecture & Development Maximilian StempfhuberRWTH Aachen University Librarystempfhuber@bth.rwth-aachen.de

  2. 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

  3. Project management(Human)Resources Infrastructure Experiments Research organisations Research programmes Research strategy Publication managementCommunication Research data Software State of the Art Proposal Management KnowledgeWealthExcellence Prizes, patentsExpertiseCommercial products ResearchInformation Information & Research Process Work programm Project proposal Project Results Transfer Wealth creation

  4. CRIS Semantic & Temporal Aspects CurrentResearch Information System Org. Unit Person Expertise CV Project Publications Events Software Patents Results FundingProgramme

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

  6. 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

  7. Same Model… … different results

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

  9. 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)

  10. 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-XML CERIF-XML Research DataRepository Finance HumanResources ProjectManagement CERIF-CRIS Projects, Persons, Org. Units,Publications, Events,Research Programmes, etc. InstitutionalRepository

  11. Community CRIS

  12. euroCRIS Strategy Enhance existing CRIS Connect CRISwith a commonCERIF wrapper euroCRIS Create standardized,reusable services Fill gaps withnew CRIS

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

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

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

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

  17. 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

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

  19. 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

  20. 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

  21. 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, …)

  22. 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

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

  24. 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

  25. 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

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

  27. 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)

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

  29. Data Exchange • Harvesting interfaces • Entity extraction • Replication • Federation • Schema mapping

  30. 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.

More Related