ࡱ>  objbj?? %]]f66    8CL 2*2S.L)))))))d+.))0 )0 0 0 )0 )0 0 #-#/~b j#I#*02*%#.0 .-#0 -#6 :   DataONE Use Case Prioritization: Years 1 5 Submitted by: DataONE Core Cyberinfrastructure Team / Virtual Data Center Technical Working Group October 7, 2009; revised October 10, 2009; revised October 13, 2009 Note: Content of this document has been merged with the DataONE architecture documentation located at: /documents/Projects/VDC/docs/service-api/api-documentation/source/prioritization.txt Further edits should be made there. Introduction The DataONE Core Cyberinfrastructure Team / Virtual Data Center Technical Working Group (CCIT/VDC TWG, hereafter CCIT) was charged with developing a prioritization of the approximately three dozen use cases developed to date. The prioritization was to be shared with the DataONE Leadership Team in order to come to agreement for the development priorities for years 1 through 5. This agreement was considered an important deliverable for the DataONE kickoff meeting in October 2009. The CCIT reviewed existing documents, including the CI Preliminary Task List, the Service Interface Prioritization diagram, the DataONE VDC June 2009 Technical Working Group Meeting Report, and the DataNetONE Implementation Plan (primarily Objective 4) see References, below. The use cases are defined in the DataONE Architecture document available at  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html. Goals and milestones expressed in the CI Preliminary Task List were foundational for developing the proposed prioritization (see Table 1). In some instances, use case implementations in the early years may be partial or limited implementations with work continuing in later years until completion. Examples of use cases that are likely to be improved over time are authentication, logging, search and retrieval, event notifications, etc. Work on other goals and milestones will begin as early as year 1, led by the appropriate working group, with the initial implementation in a subsequent year (e.g., scientific use cases; workflow support; ontology support). Certain goals and milestones (e.g., replication of data and metadata) will be met by evaluating alternatives and selecting a set of existing software applications. Additional details about Member Nodes will be provided in a separate document, forthcoming. This prioritization is mapped optimistically to the 5-year schedule: goals, milestones, and specific use cases that are the best candidates for potential deferral are indicated in the table and discussion below. The CCIT reviewed the prioritization, distributed it to the Leadership Team, and discussed the prioritization during a videoconference held October 13, 2009. Improvements identified during the videoconference were incorporated into the document, which was then distributed at the DataONE kickoff meeting held October 20-22, 2009. Goal / MilestoneYear 1Year 2Year 3Years 4-5Launch 3 Coord. / 3 Member Node networkXInitial GUID supportXFormalize service APIsXReference service / client implementationsXAuthentication: short- then long-termX1X2Search, retrieval, metadata interoperabilityX1X2X3X4DataONE User InterfaceX1X2X3X4DataONE Investigator ToolkitX1X2X3X4Replication of data and metadataXHeartbeat / health monitor (basic to robust)*X1X2X3X4Logging (basic to robust)*X1X2X3Member Node registryX1X2Additional Member NodesX1X2X3Data / metadata deposit, update, deleteXIdentity provider (external or internal)XAuthorizationXNotification of DataONE events*X1X2X3Data usage policy supportXWeb-based batch data uploadsXLaunch robust public prototypeXSupport scientific use casesXClient discovery servicesXBatch ingest for data / metadataXStress and load testingXCoordinating node failover / load balancing*XData and metadata validationXData and metadata migrationXWorkflow supportXOntology supportXProvenance supportXSupport advanced scientific use casesXCapacity monitoringXHardened infrastructureXTable  SEQ Table \* ARABIC 1: Goal / milestone summary, by year. Goals / milestones with asterisks could be deferred to the following year. X indicates the year of planned implementation. Xn indicates cyberinfrastructure goals to be met through successive releases. Shaded cells indicate activities undertaken by DataONE working groups and the CCIT in years prior to initial implementation. Year 1 Use Cases Goals and Milestones The year 1 goals and milestones for DataONE include: Launching a network consisting of three Coordinating Nodes and three Member Nodes Initial support for GUIDs (globally unique identifiers) Formalize service APIs Provide reference service / client implementations Authentication using a short-term solution Search and retrieval of data from all Member Nodes to demonstrate basic metadata interoperability (initial release) DataONE user interface (initial release) DataONE Investigator Toolkit (initial release) Replication of data and metadata between Coordinating and Member Nodes, bootstrapped using existing repositories Heartbeat / health monitoring (initial release) Infrastructure (initial release) Member Node registry services (initial release) Use Cases Authentication Using Short-term Solution  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-12-user-authentication#use-case-12-user-authentication" Use Case 12 - User Authentication: Person, via client software, authenticates against Identify Provider to establish session token. Many operations in the DataONE system require user authentication to ensure that the user's identity is known to the system, and that appropriate access controls can be executed based on the identity.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-14-system-authentication-and-authorization#use-case-14-system-authentication-and-authorization" Use Case 14 - System Authentication and Authorization: System Authentication/Authorization - Server authenticates and performs system operations (e.g. replication). This use case represents node-to-node authentication. Search and Retrieval, Indexing, Read Data and Metadata, Metadata Interoperability  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-1-crud-read#use-case-1-crud-read" Use Case 1 - CRUD Read(): Get object identified by GUID (authenticated or not, notify subscriber of access). A client has an identifier for some object within the DataONE system and is retrieving the referenced object. The DataONE system must resolve the identifier and return the object bytes after checking that the user has read privileges on the object.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-02-list-guids-by-search#use-case-02-list-guids-by-search" Use Case 02 - List GUIDs By Search: Get list of GUIDs from metadata search (anonymous and authenticated). A user performs a search against the DataONE system and receives a list of object identifiers (GUIDs) that match the search criteria. The list of GUIDs is filtered such that only objects for which the user has read permission will be returned. This use case assumes that the search is being performed by submitting a query against a CN. Replication of Data and Metadata  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-06-mn-synchronize#use-case-06-mn-synchronize" Use Case 06 - MN Synchronize: Replicate / synchronize metadata record between Member Node and Coordinating Node. As data packages, or portions thereof, are created or modified, the metadata associated with those needs to be replicated to the coordinating nodes. The presence of new or changed information on a Member Node (MN) is made known to a Coordinating Node (CN) through the status information in a ping() response. If so indicated, the CN schedules a synchronization operation with the MN, a list of changed object GUIDS is retrieved by the CN, and the CN proceeds to retrieve and process each object identified. If new data packages are present on the MN, then a MN-MN synchronization process is scheduled.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-09-replicate-mn-to-mn#use-case-09-replicate-mn-to-mn" Use Case 09 - Replicate MN to MN: Replicate data from Member Node to Member Node - (facilitated by Coordinating Node or independently but notifying Coordinating Node of operation).  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-24-mns-and-cns-support-transactions#use-case-24-mns-and-cns-support-transactions" Use Case 24 - MNs and CNs Support Transactions: Transactions - CNs and MNs should support transaction sets where operations all complete successfully or get rolled back (e.g., upload both data and metadata records). Implementation of this use case could be deferred to year 2. Basic Heartbeat / Health Monitoring (candidate for deferral to year 2)  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-10-mn-status-reports#use-case-10-mn-status-reports" Use Case 10 - MN Status Reports: Coordinating Node checks "liveness" of all Member Nodes. Implementation of this use case could be deferred to year 2. Basic Logging Infrastructure (candidate for deferral to year 2)  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-16-log-crud-operations#use-case-16-log-crud-operations" Use Case 16 - Log CRUD Operations: All CRUD operations on metadata and data are logged at each node. Implementation of this use case could be deferred to year 2.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-17-crud-logs-aggregated-at-cns#use-case-17-crud-logs-aggregated-at-cns" Use Case 17 - CRUD Logs Aggregated at CNs: All CRUD logs are aggregated at coordinating nodes. Implementation of this use case could be deferred to year 2. Basic Member Node Registry Services  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-03-register-mn#use-case-03-register-mn" Use Case 03 - Register MN: Register a new Member Node. This use case describes the technical process for addition of a new member node (MN) to the DataONE infrastructure. It is assumed that the appropriate social contracts have been formed and the MN is operational, ready to be connected. Year 2 Use Cases Goals and Milestones The year 2 goals and milestones for DataONE include: Deploy additional Member Nodes Data and metadata deposit, update, and delete Implement an external or internal identity provider Implement authorization Support notifications based upon DataONE events (initial release) Support negotiated and approved data usage policies Web-based interface for batch data uploads Search and retrieval of data from all Member Nodes (release 2) DataONE user interface (release 2) DataONE Investigator Toolkit (release 2) Heartbeat / health monitoring (release 2) Logging infrastructure (release 2) Member Node registry services (release 2) Use Cases Data and Metadata Deposit, Update, and Delete  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-04-crud-create-update-delete#use-case-04-crud-create-update-delete" Use Case 04 - CRUD (Create, Update Delete) Metadata: Create, update or delete metadata record on a Member Node. A user is creating a new metadata record on a Member Node (MN). The mechanism by which the user does this is out of scope for the DataONE system, so this use case continues from the point where a new Data Package is present on the MN. The metadata is retrieved by the CN using a pull mechanism (CN requests content from the MN).  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-05-crud-create-update-delete#use-case-05-crud-create-update-delete" Use Case 05 - CRUD (Create, Update Delete) Data: Create/Update/Delete data object in Member Node. May split out the update and delete portions to different use cases at some point in the future.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-23-owner-expunge-content#use-case-23-owner-expunge-content" Use Case 23 - Owner Expunge Content: User can find out where all copies of my data are in the system and can expunge them. Implementation of this use case could be deferred to year 3. Identity Provider  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-15-account-management#use-case-15-account-management" Use Case 15 - Account Management: User Account Management - Create new user account on Identity Provider (also edit, delete). Support Authorization  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-13-user-authorization#use-case-13-user-authorization" Use Case 13 - User Authorization: ser Authorization - Client requests service (get, put, query, delete, ...) using session token. Support Notifications Based Upon DataONE Events (candidate for deferral to year 3)  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-21-owner-subscribe-to-crud-operations#use-case-21-owner-subscribe-to-crud-operations" Use Case 21 - Owner Subscribe to CRUD Operations: Data owners can subscribe to notification service for CRUD operations for objects they own. Implementation of this use case could be deferred to year 3.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-28-derived-product-original-change-notification#use-case-28-derived-product-original-change-notification" Use Case 28 - Derived Product Original Change Notification: Relationships/Versioning - Derived products should be linked to source objects so that notifications can be made to users of derived products when source products change. Implementation of this use case could be deferred to year 3. Enhance the Logging Infrastructure  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-16-log-crud-operations#use-case-16-log-crud-operations" Use Case 16 - Log CRUD Operations: All CRUD operations on metadata and data are logged at each node.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-17-crud-logs-aggregated-at-cns#use-case-17-crud-logs-aggregated-at-cns" Use Case 17 - CRUD Logs Aggregated at CNs: All CRUD logs are aggregated at coordinating nodes.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-18-mn-retrieve-aggregated-logs#use-case-18-mn-retrieve-aggregated-logs" Use Case 18 - MN Retrieve Aggregated Logs: Member nodes can request aggregated CRUD log for {time period/object id/userid} for all of 'their' objects. Implementation of this use case could be deferred to year 3.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-19-retrieve-object-download-summary#use-case-19-retrieve-object-download-summary" Use Case 19 - Retrieve Object Download Summary: General public can request aggregated download usage information by object id. Implementation of this use case could be deferred to year 3.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-20-owner-retrieve-aggregate-logs#use-case-20-owner-retrieve-aggregate-logs" Use Case 20 - Owner Retrieve Aggregate Logs: Data owners can request aggregated CRUD log for {time period/object id} for all of 'their' objects. Implementation of this use case could be deferred to year 3. Support Data Usage Policies  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-08-replication-policy-communication#use-case-08-replication-policy-communication" Use Case 08 - Replication Policy Communication: Communication of replication policy metadata between Member Nodes and Coordinating Nodes. The replication policy of Member Nodes (MN) indicates factors such as the amount of storage space available, bandwidth constraints, the types of data and metadata that can be managed, and perhaps access control restrictions. This information is used by Coordinating Nodes (CN) to balance the distribution of data packages throughout the DataONE system to achieve the goals of data package persistence and accessibility.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-31-manage-access-policies#use-case-31-manage-access-policies" Use Case 31 - Manage Access Policies: Manage Access Policies - Client can specify access restrictions for their data and metadata objects. Also supports release time embargoes. Year 3 Use Cases Goals and Milestones The year 3 goals and milestones for DataONE include: Deploy additional Member Nodes Launching a robust public prototype Support selected scientific use cases Authentication using a long-term solution Implement client discovery services Batch ingest support Conducting stress and load testing Implementing Coordination Node failover and load balancing Search and retrieval of data from all Member Nodes (release 3) DataONE user interface (release 3) DataONE Investigator Toolkit (release 3) Heartbeat / health monitoring (release 3) Logging infrastructure (release 3) Support notifications based upon DataONE events (release 2) Use Cases Authentication Using a Long-Term Solution  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-12-user-authentication#use-case-12-user-authentication" Use Case 12 - User Authentication: Person, via client software, authenticates against Identify Provider to establish session token. Many operations in the DataONE system require user authentication to ensure that the user's identity is known to the system, and that appropriate access controls can be executed based on the identity.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-14-system-authentication-and-authorization#use-case-14-system-authentication-and-authorization" Use Case 14 - System Authentication and Authorization: System Authentication/Authorization - Server authenticates and performs system operations (e.g. replication). This use case represents node-to-node authentication. Client Discovery Services  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-33-search-for-data#use-case-33-search-for-data" Use Case 33 - Search for Data: Clients should be able to search for data using CN metadata catalogs.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-34-cns-support-other-discovery-mechanisms-e-g-google#use-case-34-cns-support-other-discovery-mechanisms-e-g-google" Use Case 34 - CNs Support Other Discovery Mechanisms (e.g. Google): Coordinating Nodes publish metadata in formats for other discovery services like Google/Libraries/GCMD/etc. Batch Ingest  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-07-cn-batch-upload#use-case-07-cn-batch-upload" Use Case 07 - CN Batch Upload: Batch Operations - Coordinating Node requests metadata /data list from new Member Node and then batch upload (disable indexing for example to improve insert performance). Coordination Node Failover and Load Balancing (candidate for deferral to years 4-5)  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-29-cn-load-balancing#use-case-29-cn-load-balancing" Use Case 29 - CN Load Balancing: Load Balancing - Requests to coordinating nodes are load balanced. Implementation of this use case could be deferred to years 4-5. Complete Logging Infrastructure  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-22-link-citation-report-for-owner#use-case-22-link-citation-report-for-owner" Use Case 22 - Link/Citation Report for Owner: User can get report of links/cites my data (also can view this as a referrer log). Years 4-5 Use Cases Goals and Milestones The year 4-5 goals and milestones for DataONE include: Deploy additional Member Nodes Data and metadata validation Data and metadata migration Workflow support Ontology support Provenance support Support for general and innovative scientific use cases (subsetting, translation, semantic interoperability, advanced visualization, etc.) Capacity monitoring Hardening of overall infrastructure into a robust system Search and retrieval of data from all Member Nodes (release 4) DataONE user interface (release 4) DataONE Investigator Toolkit (release 4) Heartbeat / health monitoring (release 4) Support notifications based upon DataONE events (release 3) Use Cases Data and Metadata Validation  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-25-detect-damaged-content#use-case-25-detect-damaged-content" Use Case 25 - Detect Damaged Content: System should scans for damaged/defaced data and metadata using some validation process.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-26-data-quality-checks#use-case-26-data-quality-checks" Use Case 26 - Data Quality Checks: System performs data quality checks on data. Data and Metadata Migration  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-27-metadata-version-migration#use-case-27-metadata-version-migration" Use Case 27 - Metadata Version Migration: CN should support forward migration of metadata documents from one version to another within a standard and to other standards. Workflow Support  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-11-crud-workflow-objects#use-case-11-crud-workflow-objects" Use Case 11 - CRUD Workflow Objects: Create / update / delete / search workflow objects. Provenance Support  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-28-derived-product-original-change-notification#use-case-28-derived-product-original-change-notification" Use Case 28 - Derived Product Original Change Notification: Relationships/Versioning - Derived products should be linked to source objects so that notifications can be made to users of derived products when source products change.  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-32-transfer-object-ownership#use-case-32-transfer-object-ownership" Use Case 32 - Transfer Object Ownership: User or organization takes over 'ownership' of a set of objects (write access for orphaned records). Complete Heartbeat / Health Monitoring  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" \l "use-case-30-mn-outage-notification#use-case-30-mn-outage-notification" Use Case 30 - MN Outage Notification: MN can notify CN about pending outages, severity, and duration, and CNs may want to act on that knowledge to maintain seamless operation. References CI Preliminary Task List, available at  HYPERLINK "https://repository.dataone.org/documents/Meetings/20090210-mat-santa-barbara-mtg/CI_preliminary_tasklist_021809.xls" https://repository.dataone.org/documents/Meetings/20090210-mat-santa-barbara-mtg/CI_preliminary_tasklist_021809.xls. DataONE Architecture, available at:  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html" https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html. DataNetONE Implementation Plan (Objective 4), available at: [need URI]. DataONE VDC June 2009 Technical Working Group Meeting Report,  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/20090602_04_ABQ_Meeting/20090604MeetingReport.pdf" https://repository.dataone.org/documents/Projects/VDC/docs/20090602_04_ABQ_Meeting/20090604MeetingReport.pdf. Service Interface Prioritization (diagram), available at  HYPERLINK "https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-diagrams/service-api-layers.png" https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-diagrams/service-api-layers.png. DataONE Use Case Prioritization: Years 1 5  DATE \@ "M/d/yyyy" 11/10/2009  FILENAME DataOneUseCasePrioV.2.doc Page  PAGE 10 of  NUMPAGES 10 @ A { } g   !/j_f  &ڻ hc[e5hU hc[e5CJOJQJhdhf<h/0"h hh )!jhc[e>*B*Uphjhc[e>*B*Uphhc[e>*B*phh|h:h!h`koh6/h"Vhc[e8-< = `a$If   NH???? $$Ifa$$Ifkd9$$Ifl44rt"Z0"64 laf4  !#$%&SMDDDD $$Ifa$$Ifkd$$Iflrt"Z0"64 la&'>@ABCSMDDDD $$Ifa$$Ifkd$$Iflrt"Z0"64 la&>Cot !"#$%&'()*MRعh"Vh!K5H*h*h!K5H* h!K5h!K h!K5H*h*h!K5h*h"V5H*h*h"V5 h"V5h"Vh"Vh"V5H*h"Vhc[e5H* h"V5H* hc[e5hc[e:CDoqrstSMDDDD $$Ifa$$Ifkds$$Iflrt"Z0"64 latuSMDDDD $$Ifa$$Ifkd.$$Iflrt"Z0"64 laSMD888 $$Ifa$gd!K $$Ifa$$Ifkd$$Iflrt"Z0"64 laSMAAAA $$Ifa$gd!K$Ifkd$$Iflrt"Z0"64 la"%(+SMAAAA $$Ifa$gd!K$Ifkd_$$Iflrt"Z0"64 la+,MOPQRSMDDDD $$Ifa$$Ifkd$$Iflrt"Z0"64 laRSSMAAAA $$Ifa$gd!K$Ifkd$$Iflrt"Z0"64 la"LQ`e6;]b{ !&:?fkh"Vh!K5mHsHh"Vh!KmHsHh*h!K5H* h!K5h*h!K5h!K h!K5H*NSMAAA8 $$Ifa$ $$Ifa$gd!K$Ifkd $$Iflrt"Z0"64 laSMA888 $$Ifa$ $$Ifa$gd!K$IfkdK $$Iflrt"Z0"64 laSMD888 $$Ifa$gd!K $$Ifa$$Ifkd $$Iflrt"Z0"64 la 82)) $$Ifa$$Ifkd $$Iflrt"Z 0"64 lap !"#L/)$Ifkd $$Iflrt"Z 0"64 lap $$Ifa$LMOPQR/kd $$Iflrt"Z 0"64 lap $$Ifa$R`acde $$Ifa$$Ifef82) $$Ifa$$Ifkd$$Iflrt"Z 0"64 lap $$Ifa$ $$Ifa$gd!K82)) $$Ifa$$Ifkd$$Iflrt"Z 0"64 lap/)$Ifkd$$Iflrt"Z 0"64 lap $$Ifa$/kdo$$Iflrt"Z 0"64 lap $$Ifa$Dkd_$$Iflrt"Z0"64 la $$Ifa$$If $$Ifa$gd!K $$Ifa$67-' $$Ifa$$Ifkd($$Iflrt"Z 0"64 lap78:;<$kd.$$Iflrt"Z 0"64 lap $$Ifa$<]^_ab $$Ifa$$Ifbc{|-' $$Ifa$$Ifkd4$$Iflrt"Z 0"64 lap|}$kd:$$Iflrt"Z 0"64 lap $$Ifa$ $$Ifa$$If-' $$Ifa$$Ifkd@$$Iflrt"Z 0"64 lap $$Ifa$"$IfkdT$$Iflrt"Z (0"64 lap( $$Ifa$ "$Ifkdp$$Iflrt"Z (0"64 lap(     $$Ifa$!"$Ifkd$$Iflrt"Z (0"64 lap(!"#$& $$Ifa$&':"$Ifkd$$Iflrt"Z (0"64 lap(:;<=? $$Ifa$?@f"$Ifkd$$Iflrt"Z (0"64 lap(fghik $$Ifa$kl"$Ifkd$$Iflrt"Z (0"64 lap( $$Ifa$dez{89Z[\o p !!H"I"a"b"d"##q$r$$$$$R&S&''#'$'%'))*****J+K+",#,Q,R,S,--<.=.\.].^._./////ŻŻh!KB*CJphh!K>*B*phjh!K>*B*Uphh h!KH*h!KmHnHujh!KUh!K h!K5J"$Ifkd$$Iflrt"Z (0"64 lap( $$$Ifa$gd!K $$Ifa$.?" kdB $$Iflrt"Z (0"64 lap(?T*]%TFPyzL!M!!!##/&0&Q&^ & FQ&R&))I+J+9-:---..//y0{011 2 2334;4Z444 & F^////x0y0{0|0I1J1s1t1u1v1 222222266z7{7777788496979::0:1:2:::;;;;;W<X<==4=5=6=7===h>i>>>>B?C?@@O@P@Q@R@@@AABBB)C*CCC D Dh!K>*B*CJphh!Kh!KB*CJphh!K>*B*phjh!K>*B*UphQ445J5u5556*6M6w66665969::C<D<V<W<====>>^ & F & Fgd!K>A?B?@@CC(C)CNDPDEE$G%GHH`JaJ}J~JMMNO$OYOxO & F^ D D DMDNDPDQDEEHEIEJEKEEENFOFxFyFzF{F$G%G&GGG,H-H.HHHIIIIII~JJVKWKKKKMMKNLNpNqNrNQQRRRRRSSTTTTTUUpVqVVVVVVVVWWXXXXXXJYKYhYjh!K>*B*Uphh!Kh!KB*CJphh!K>*B*phVxOOOOP%PHPPPPQ8Q[QQQQQSSUUUUVVXXX^ & Fgd!K & FXXZZlZmZ[[[E]Y]n]]]]]^^2^^^ _I_l___ & Fgd!K & F[$\$^hYiYjYkYmZnZ'[([G[H[I[[[\\\\\#`$``` a aaagahaiaja'b(bIbJbKbLbbbccdcccc#d$ddd e e eUeVeEfFfffff-g.g/g0ggg!h"h#h$hhhhhwixiiiii\j]jijjh!KUh!Kh!KB*CJphh!K>*B*phjh!K>*B*UphP__`"`#`haiaybzbbbdd"d#d@eAeTeUe.g/ghhhh*j5jgd!K^ & Fgd!KijjjjjSkTk{k|k}kkkkalblcldllllllgmimjmkmmmmmnn"nnnnnnnnn+o,o-oAoBoϰ}s}h!KCJOJQJjh!KCJOJQJUh!KOJQJ hG8*h!Kj5(h!KUj%h!KU!j#h!K>*B*Uphjh!K>*B*Uphh!K>*B*phhyh!K0Jjh!KUj^!h!KUh!K hh!K-5jWkXkdlelllmmn+o,ooooo 0^`0gd!KBoLoMoNoOoYoZosotozo{ooooooooooooooȼȫȼȼȫا hG8*h!Kh!K!h!K0JCJOJQJmHnHuh!K0JCJOJQJjh!K0JCJOJQJUh!KCJOJQJjh!KCJOJQJUh!KCJOJQJmHnHu# 01h/ =!"#$%9DyK khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.htmlyK https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.htmlyX;H,]ą'c$$If!vh5Z5555#vZ#v#v:V l440"65Z554f4$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z554$$If!vh5Z5555#vZ#v#v:V l0"65Z55/ 4$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l0"65Z55/ 4$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z554p$$If!vh5Z5555#vZ#v#v:V l 0"65Z55/ 4p$$If!vh5Z5555#vZ#v#v:V l (0"65Z554p(($$If!vh5Z5555#vZ#v#v:V l (0"65Z55/ 4p($$If!vh5Z5555#vZ#v#v:V l (0"65Z554p($$If!vh5Z5555#vZ#v#v:V l (0"65Z554p(($$If!vh5Z5555#vZ#v#v:V l (0"65Z55/ 4p($$If!vh5Z5555#vZ#v#v:V l (0"65Z554p(($$If!vh5Z5555#vZ#v#v:V l (0"65Z55/ 4p($$If!vh5Z5555#vZ#v#v:V l (0"65Z554p(]DyK thttps://repository.dataone.org/documents/Meetings/20090210-mat-santa-barbara-mtg/CI_preliminary_tasklist_021809.xlsyK https://repository.dataone.org/documents/Meetings/20090210-mat-santa-barbara-mtg/CI_preliminary_tasklist_021809.xlsyX;H,]ą'c9DyK khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.htmlyK https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.htmlyX;H,]ą'cADyK mhttps://repository.dataone.org/documents/Projects/VDC/docs/20090602_04_ABQ_Meeting/20090604MeetingReport.pdfyK https://repository.dataone.org/documents/Projects/VDC/docs/20090602_04_ABQ_Meeting/20090604MeetingReport.pdfyX;H,]ą'c9DyK khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-diagrams/service-api-layers.pngyK https://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-diagrams/service-api-layers.pngyX;H,]ą'c666666666vvvvvvvvv66666686666666666666666666666666666666666666666666666666hH6666666666666666666666666666666666666666666666666666666666666666666666666662 0@P`p2( 0@P`p 0@P`p 0@P`p 0@P`p 0@P`p 0@P`p8XV~_HmH nH sH tH @`@ NormalCJ_HaJmH sH tH Z@Z  Heading 1$<@&5CJ KH OJQJ\^JaJ \@\  Heading 2$<@& 56CJOJQJ\]^JaJV@V  Heading 3$<@&5CJOJQJ\^JaJDA`D Default Paragraph FontVi@V  Table Normal :V 44 la (k (No List 88 apple-style-span6U@6 Hyperlink >*B*ph4O4 firstdd[$\$4@"4 Header  !4 @24 Footer  !.)@A. Page Number@"@@  Caption xx5CJ\aJPK![Content_Types].xmlj0 u$Nwc$ans@8JbVKS(.Y$8MVgLYS]"(U֎_o[gv; f>KH|;\XV!]օ Oȥsh]Hg3߶PK!֧6 _rels/.relsj0 }Q%v/C/}(h"O = C?hv=Ʌ%[xp{۵_Pѣ<1H0ORBdJE4b$q_6LR7`0̞O,En7Lib/SeеPK!kytheme/theme/themeManager.xml M @}w7c(EbˮCAǠҟ7՛K Y, e.|,H,lxɴIsQ}#Ր ֵ+!,^$j=GW)E+& 8PK!\theme/theme/theme1.xmlYOoE#F{o'NDuر i-q;N3' G$$DAč*iEP~wq4;{o?g^;N:$BR64Mvsi-@R4Œ mUb V*XX! cyg$w.Q "@oWL8*Bycjđ0蠦r,[LC9VbX*x_yuoBL͐u_. DKfN1엓:+ۥ~`jn[Zp֖zg,tV@bW/Oټl6Ws[R?S֒7 _כ[֪7 _w]ŌShN'^Bxk_[dC]zOլ\K=.:@MgdCf/o\ycB95B24S CEL|gO'sקo>W=n#p̰ZN|ӪV:8z1f؃k;ڇcp7#z8]Y / \{t\}}spķ=ʠoRVL3N(B<|ݥuK>P.EMLhɦM .co;əmr"*0#̡=6Kր0i1;$P0!YݩjbiXJB5IgAФ޲a6{P g֢)҉-Ìq8RmcWyXg/u]6Q_Ê5H Z2PU]Ǽ"GGFbCSOD%,p 6ޚwq̲R_gJSbj9)ed(w:/ak;6jAq11_xzG~F<:ɮ>O&kNa4dht\?J&l O٠NRpwhpse)tp)af] 27n}mk]\S,+a2g^Az )˙>E G鿰L7)'PK! ѐ'theme/theme/_rels/themeManager.xml.relsM 0wooӺ&݈Э5 6?$Q ,.aic21h:qm@RN;d`o7gK(M&$R(.1r'JЊT8V"AȻHu}|$b{P8g/]QAsم(#L[PK-![Content_Types].xmlPK-!֧6 /_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!\theme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK] g..&/ DhYijBoo:?Gjpsvxz &Ct+R LRe7<b| !&:?fk?Q&4>xOX_5jo;<=>@ABCDEFHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghiklmnoqrtuwy z8ZoHaqR#!""J#"$Q$%<&\&'''{(I)s) ***.z//61202233W45455h66B78O889:);; <P<=H==N>x>%??,@@AA~BVCCEKFpFIJJKLLMpNNNOPPJQhQmR'SGSSTT#XX YiY'ZIZZc[[#\\ ]U]E^^/__!``waa\bbSc|ccaddjeefffgX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.CNP[u|!8@0(  B S  ?gg;BH[ )0q{y  v}cepx%,)0 <Aot1$4$9$<$c$f$k$n$y&&p)s)Q+X+*,1,,,----n0u077E=H=>>3E:EHGOGHHHH|II'K.KOOUUkVuVIWPWlWsWWWaaXc_cedodddfggg [` 9$<$66OOfgg:::::X?T\Mh ^`OJQJo(h^`OJQJ^Jo(hHohpp^p`OJQJo(hHh@ @ ^@ `OJQJo(hHh^`OJQJ^Jo(hHoh^`OJQJo(hHh^`OJQJo(hHh^`OJQJ^Jo(hHohPP^P`OJQJo(hHX?T\!K   ! # $ % & ' > @ A B C D o q r s t u    " % ( + , M O P Q R S  !"#LMOPQR`acdef678:;<]^_abc{|}    !"#$&':;<=?@fghiklfgg|@gP@UnknownGTimes New Roman5Symbol3 Arial?1M Courier New;Wingdings"1h4FUF-lFP]0T +=V ,!4cgf 2qH(?"V0,DataOne Use Case Prioritization: Years 1  5Robert Sandusky Dave Vieglais  Oh+'0( @L p |  '0DataOne Use Case Prioritization: Years 1 5Robert Sandusky Normal.dotmDave Vieglais80Microsoft Macintosh Word@n|T@n FL@B=F@λ~b 0T ՜.+,D՜.+,` hp  ' UIC LIBRARY+cg -DataOne Use Case Prioritization: Years 1 5 Title: 8@ _PID_HLINKS'AX:t/khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-diagrams/service-api-layers.pngPTdmhttps://repository.dataone.org/documents/Projects/VDC/docs/20090602_04_ABQ_Meeting/20090604MeetingReport.pdfPm&~khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.htmlPj4{thttps://repository.dataone.org/documents/Meetings/20090210-mat-santa-barbara-mtg/CI_preliminary_tasklist_021809.xlsP8'xkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-30-mn-outage-notification#use-c1yukhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-32-transfer-object-ownership#us)jrkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-28-derived-product-original-cha38okhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-11-crud-workflow-objects#use-ca$}lkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-27-metadata-version-migration#uswikhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-26-data-quality-checks#use-casekrfkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-25-detect-damaged-content#use-c:+ckhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-22-link-citation-report-for-ownk`khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-29-cn-load-balancing#use-case-2wm]khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-07-cn-batch-upload#use-case-07-mdZkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-34-cns-support-other-discovery-s~Wkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-33-search-for-data#use-case-33-$gTkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-14-system-authentication-and-au3dQkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-12-user-authentication#use-case*4Nkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-31-manage-access-policies#use-c(1Kkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-08-replication-policy-communicas'Hkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-20-owner-retrieve-aggregate-logx(Ekhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-19-retrieve-object-download-sumypBkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-18-mn-retrieve-aggregated-logs#~3?khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-17-crud-logs-aggregated-at-cns#,!<khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-16-log-crud-operations#use-case)j9khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-28-derived-product-original-cha916khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-21-owner-subscribe-to-crud-oper993khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-13-user-authorization#use-case-hv0khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-15-account-management#use-case-qr-khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-23-owner-expunge-content#use-ca`p*khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-05-crud-create-update-delete#usap'khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-04-crud-create-update-delete#us8n$khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-03-register-mn#use-case-03-regi~3!khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-17-crud-logs-aggregated-at-cns#,!khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-16-log-crud-operations#use-casemrkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-10-mn-status-reports#use-case-1bskhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-24-mns-and-cns-support-transact-&khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-09-replicate-mn-to-mn#use-case-.okhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-06-mn-synchronize#use-case-06-mh1khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-02-list-guids-by-search#use-cas~r khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-1-crud-read#use-case-1-crud-rea$g khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-14-system-authentication-and-au3dkhttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.html)use-case-12-user-authentication#use-casem&khttps://repository.dataone.org/documents/Projects/VDC/docs/service-api/api-documentation/Architecture.htmlP  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{}~Root Entry F~bData |n*1Table.WordDocument%SummaryInformation(DocumentSummaryInformation8<CompObj` F Microsoft Word 97-2004 DocumentNB6WWord.Document.8