Researcher ID Information Flow

Slides:



Advertisements
Similar presentations
The worlds libraries. Connected. VIAF & ISNI Virtual International Authority File (VIAF) & International Standard Name Identifier (ISNI) by Titia van der.
Advertisements

Chapters 7 & 9 System Scope
Ch 12: Object-Oriented Analysis
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
A use case describes one “case” of how a user can use the system.
System Analysis and Design
DATA FLOW DIAGRAMS IT 155.
Chapter 10: Architectural Design
Process Modeling SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Anila Angjeli 1 APARSEN - Interoperability of PI workshop, iPRES, Lisbon, 5 September 2013 VIAF and Member of the Board of directors of ISNI-IA.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
PHASE 2: SYSTEMS ANALYSIS
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
1 Structuring Systems Requirements Use Case Description and Diagrams.
University of Southern California Center for Systems and Software Engineering Common mistakes in Core FC Package.
Term project Team 2 ( K.D. Kang, J.H. Lim, Y.J. W ) Online Document Management System.
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
IS3320 Developing and Using Management Information Systems Lecture 16: Data-Flow Diagrams 1 (Intro to Context-Level diagrams) Rob Gleasure
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Object-Oriented Systems Analysis and Design Using UML Systems Analysis and Design,
Identifying classes, Packages and drawing class Diagrams, Object Diagrams and composite structure diagrams Week 07 1.
EuroCRIS strategic membership meeting Barcelona – 9-11 November 2015 Role of ISNI in research information management Titia van der Werf-Davelaar Senior.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
DATA FLOW DIAGRAMS.
Copyright © 2014 Pearson Canada Inc. 5-1 Copyright © 2014 Pearson Canada Inc. Application Extension 5a Database Design Part 2: Using Information Technology.
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Introduction to Rational Rose 2000 Create Use Case Model.
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes & Modeling Processes with Swimlane Diagrams.
Data Modeling Using the Entity- Relationship (ER) Model
Method – Notation 8 Hours.
Application Extension 5a
Database Development Lifecycle
Chapter 3 DOCUMENTING ACCOUNTING SYSTEMS
CHAPTER
Information Delivery Manuals: Process Mapping
Systems Documentation Techniques
Chapter 4: Business Process and Functional Modeling, continued
Systems Analysis and Design
Identifying Data Flows
Chapter 5: Structural Modeling
Entity-Relationship Model
Data Management Agenda
Rob Gleasure IS3320 Developing and Using Management Information Systems Lecture 14: Data-Flow Diagrams 1 (Context-Level.
Object-Oriented Systems Analysis and Design Using UML
System Process Modeling
CIS 764 Database Systems Engineering
System Modeling Chapter 4
Linking persistent identifiers at the British Library
The Process of Object Modeling
Critical Warnings and Alerts
eDIRECT: User Management
Chapter 6 Normalization of Database Tables
Software Engineering Lecture #11.
Working Group on Population and Housing Censuses
CS 425/625 Software Engineering Architectural Design
IMAT5205 Systems Analysis and Design
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Requirement Analysis using
Entity-Relationship Diagram (ERD)
Class Diagram.
Chapter 4: documenting information systems
Design Yaodong Bi.
CIS 375 Bruce R. Maxim UM-Dearborn
Use Case Analysis – continued
Appendix A Object-Oriented Analysis and Design
Chapter 4 System Modeling.
Appendix A Object-Oriented Analysis and Design
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Entity-Relationship Design
Presentation transcript:

Researcher ID Information Flow This diagram depicts the flow of information describing researchers and identified researcher outputs such as publications among classes of actors and systems.  Each category of actor is depicted with an icon and a caption.  An arrow going from one entity to another is used to indicate that information flows from one entity to the other. Specific entities (Crossref, ISNI, VIAF, ORCID) are indicated with bold text; all other entities represent a category of entity within the general types—public aggregator, internal aggregator or public view. The presence or absence of arrows is based on analyzing the detailed research networking systems characteristics profiles[1]. Arrows are shown in the diagram wherever there is at least one pair of profiled entities of those categories transmitting information. The researcher identifier information flow diagram reveals several patterns: Information flow is quite complex overall, especially between public aggregators and private aggregators. Most of the information flow is one way—there are few automatic or systematic channels for corrections or annotations at later stages to flow back up to public aggregator sources, or to the actors providing them. ISNI—which focuses on managing links between member identifier systems and databases—is an exception. It tracks all sources, and corrections are fed back to the source as they are made. The interoperability flows between ISNI and ISNI registration agencies, and between ISNI and VIAF, are indicated in the diagram by bidirectional arrows. Many actors are contributing to multiple public views of Researcher ID information. Information provided by the same class of actor may flow through multiple (possible concurrent) paths to internal aggregator systems and public views—suggesting the potential for duplication and inconsistency. Individual categories of public views seldom represent more than one type of internal aggregator. A key question is how corrections or updates can be communicated between systems. Researchers are frustrated when they see errors in their profile, works incorrectly assigned to them or works missing. Even if the information is corrected in the local instance, it often is not reflected in the aggregated databases or hubs. [1]. See the OCLC Research Registering Researchers in Authority Files report at http://www.oclc.org/content/dam/research/publications/library/2014/oclcresearch-registering-researchers-2014.pdf for more information.