1 / 29

@ euroCRIS Madrid, November 2012: Federation and the n ecessity of standards : a case study

@ euroCRIS Madrid, November 2012: Federation and the n ecessity of standards : a case study. Rudolf Weiss. Topics for today. Federated Scenarios What is a federation? What are the challenges in federated scenarios How to cope with these challenges? How can standards help? Use Cases

cyrah
Télécharger la présentation

@ euroCRIS Madrid, November 2012: Federation and the n ecessity of standards : a case study

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. @ euroCRIS Madrid, November 2012: Federationandthenecessityofstandards: a casestudy Rudolf Weiss

  2. Topics for today • Federated Scenarios • What is a federation? • What are the challenges in federated scenarios • How to cope with these challenges? • How can standards help? • Use Cases • Brief Introduction to CONVERIS • Sunderland • Aristoteles

  3. Topics for today • Federated Scenarios • What is a federation? • What are the challenges in federated scenarios? • How to cope with these challenges? • How can standards help? • Use Cases • Brief Introduction to CONVERIS • Sunderland • Aristoteles

  4. Motivation anddrivers • In general • Outsourcing of functionalities • Problem solving in a collaborative way • Improving data quality  Striving for more efficiency • Reporting • Measurement • Comparison  Impact Measurement

  5. Federation - Definitions • Definitions of a federation “A federation can be understood as a collection of trust realms that have established a degree of trust. The level of trust between them may vary.” [Djordjevic& Dimitrakos2005] “Federation refers to the establishment of some or all of business agreements, cryptographic trust, user identifiers and attributes between decentralized security and policy domains.” [Madsen 2004]

  6. Federation - Characteristics • Characteristics of a federation • Autonomy • Trust • Delegation • Decentralization • Federation both can be within or outside of an organisation • Scopeoffunctionality • Exchange databased • Periodically via fileexchange • Message-basedatruntime • Dropbox-likefunctionality • Sharing e.g. searchfunctionality

  7. DegreeofCoupling • Loosely-coupled federation • Exchange of information via messages, e.g. CERIF XML • Asynchronous communication • Independence from other systems concerning availability, performance, scalability, … • Tightly-coupled federation • Inter-organizational processes • Enhanced scope of functionality • Synchronous communication • Dependency concerning availability, performance, robustness, ...

  8. Federated Scenario - Challenges CardSpace CardSpace CardSpace Shibboleth Shibboleth Shibboleth Fullname DoB E-Mail … Fullname DoB E-Mail … Fullname DoB E-Mail … Firstname Lastname Mail … Firstname Lastname Mail … Firstname Lastname Mail … Fn sn Affiliation … Fn sn Affiliation … Fn sn Affiliation … Firstname Age Mailaddress … Firstname Age Mailaddress … Firstname Age Mailaddress …

  9. Challenges - rapidly evolving Research Information Ecosystem YouTube Research funders LinkedIn GrantsFinder Social Media Skype Research Professional Facebook Twitter Pivot COS COS ... pFact SAP Patent Offices Agresso ... ... Bibliometrics Google Sherpa / RoMEO Web of Science Publishers CrossRef Open Access SciVal

  10. Challenges - rapidly evolving Research Information Ecosystem YouTube LinkedIn Social Media Research funders GrantsFinder Skype Research Professional Research Professional Facebook Facebook Twitter Twitter OSN FO Pivot COS COS Patent Offices SAP Finance TT pFact ... Agresso ... Publications ... Bibliometrics Google Sherpa / RoMEO Web of Science Publishers CrossRef Open Access SciVal

  11. Challenges - rapidly evolving Research Information Ecosystem YouTube LinkedIn Social Media Research funders GrantsFinder Skype Research Professional Research Professional Facebook Facebook • How to cope with: • unstructured information? • lack of common identifiers? • unstructured processes? • convergence vs. integration? Twitter Twitter OSN FO Pivot COS COS Patent Offices SAP Finance TT pFact ... Agresso ... Publications ... Bibliometrics Google Sherpa / RoMEO Web of Science Publishers CrossRef Open Access SciVal

  12. Necessity of Standards YouTube LinkedIn Social Media Research funders GrantsFinder Skype Research Professional Research Professional Facebook Facebook Twitter Twitter OSN FO Pivot COS COS Web services Standards XML VIVO Patent Offices SAP Communication Standards Finance TT pFact ORCID CASRAI ... CERIF ITIL Agresso CMMI ... ... Publications ... Bibliometrics Google Sherpa / RoMEO Web of Science Publishers CrossRef Open Access SciVal

  13. cc cc cc cc cc Ideal Federated Scenario • Required: • Common information model, syntax and semantics • Standardized communication, i.e. protocol and format • Stable interfaces • Common identifiers

  14. Topics for today • Federated Scenarios • What is a federation? • What are the challenges in federated scenarios • How to cope with these challenges? • How can standards help? • Use Cases • Brief Introduction to CONVERIS • Sunderland • Aristoteles

  15. Research lifecycle Research Information

  16. Research lifecycle • Publications • Patent • Awards • Person • Projects • Org. Unit ? Who, withwhom, what, when , how?

  17. Research lifecycle Processes • Timely • Complete • Correct • User oriented ? Collecting , Validating, Maintaining, Archiving

  18. Fragmentation, data inconsistency, high costs, ... ? HR Institutional repository Unique & joint IDs CMS Finance Where are the gaps CONVERIS Text strings or relations Ad-hoc or systematic processes Patents Grants & Contracts Up-to-date or out-of-date Data quality & duplicates Login server Student records Local IT-infrastructure Patent offices Funding bodies PubMed Scopus Web of Science

  19. Complete Research Information System Login server Authentication Person data Legacy data Web pages(CMS) Researcher CVs Research interests HR Person data Org data Migration Business Intelligence Cross-analyses Finance Project data Transactions Institutional Repository Research papers & other output Pricing & Costing Applications Budgets • Utilisation • Day-to-day management • Reports: • Publications & bibliometrics • Applications & contracts • PhD students & progress • Patents & licensing • Annual/REF reports & other returns • Networks & collaborations • Exports • CVs • Visibility over the web Patents & Licenses Patent data Student records Student data Internal IT-infrastructure • Prepopulation and (auto-)updates • Journals/Publishers • Journal policy (Sherpa / RoMEO) • DOIs (CrossRef) • Classfications (ISI, OECD, ISO, etc.) • Organisations Project data Publication data Patent data National Funders & EC WoS, Scopus PubMed, ... EPO

  20. Research Information: A growing concept for CONVERIS RESEARCH INFORMATION SYSTEM CAMPUS MANAGEMENT SYSTEMS Graduate Students Student Lifecycle Research Lifecycle Grants Management HR & Finance BUSINESS IT SYSTEMS Finance

  21. Use Cases • Federation within an organisation • University of Sunderland • Loosely-coupled federation • Sweden ScienceNet • Tightly-coupled federation • Aristoteles

  22. Use Case I – University of Sunderland

  23. University of Sunderland Person Records Project Applications Projects Student Records Publication Records

  24. Federation inside a University: University of Sunderland • Integration via CERIF-XML for interoperability between internal systems: HR, Student records, Finance, Institutional Repository and Projects to CONVERIS • CERIF experience on both sides • 2 months implementation • No significant overhead compared to non-CERIF integration • Internal systems equipped for the future • Resumee: Having a common understanding of the data decreases effort (time and resources) tremendously

  25. Use Case II – Aristoteles

  26. Aristoteles I EURAC CONVERIS FUB SIAG Aristoteles ...

  27. Aristoteles II EURAC EURAC CONVERIS FUB SIAG FUB SIAG Aristoteles ... ...

  28. Aristoteles • Enhanced range of functionality • Common use of publication search • Inter-organisational business process • Dropbox-like sharing of information • Using CERIF for the exchange of information • UUIDs as common identifier for projects, publications and persons • ORCID as unique identifier for a researcher (planned)

  29. Thank you for listening. Rudolf Weiss r.weiss@avedas.com +49 171 706 25 18 +49 721 354 90 10 Skype ID: rudolf697 Dr. Thorsten Hoellrigl t.hoellrigl@avedas.com +49 152 5310 47 01 +49 721 354 90 24 Skype ID: t.hoellrigl AVEDAS AG Web: www.avedas.com Twitter: @avedas_com LinkedIn: http://www.linkedin.com/company/avedas-ag Facebook: http://www.facebook.com/AVEDAS.AG

More Related