|
|
| Line 1: |
Line 1: |
| − | Use Case EIE05: Manage Collection Catalog
| |
| | | | |
| − | for
| |
| − |
| |
| − | Earth Information Exchange
| |
| − |
| |
| − |
| |
| − | Version 1.0 draft
| |
| − |
| |
| − | Prepared by John Kozimor
| |
| − |
| |
| − | NGDC
| |
| − |
| |
| − | Nov. 11, 2006
| |
| − |
| |
| − | Revision History
| |
| − |
| |
| − |
| |
| − |
| |
| − | Name
| |
| − |
| |
| − | Date
| |
| − |
| |
| − | Reason For Changes
| |
| − |
| |
| − | Version
| |
| − |
| |
| − | John Kozimor
| |
| − |
| |
| − | 11/18/2006
| |
| − |
| |
| − | Initial Draft
| |
| − |
| |
| − | 1.0
| |
| − |
| |
| − |
| |
| − | =1.Use Case Identification=
| |
| − |
| |
| − | ==1.1.Use Case Number==
| |
| − |
| |
| − | EIE05
| |
| − |
| |
| − | ==1.2.Use Case Name==
| |
| − |
| |
| − | Manage Collection Catalog
| |
| − |
| |
| − | =2.Use Case Definition=
| |
| − |
| |
| − | Data Provider/Publisher add metadata records to the portal dataset catalog and update or delete those records.
| |
| − |
| |
| − | ==2.1.Actors==
| |
| − |
| |
| − | *1.Data Provider/Publisher
| |
| − |
| |
| − | ==2.2.Preconditions==
| |
| − |
| |
| − | *1.Data Provider/Publisher is registered with GOS.
| |
| − | *2.Data Provider/Publisher has appropriate access privileges.
| |
| − | *3.Data Provider/Publisher must have metadata that is compliant with EIE standards.
| |
| − | *4.Data Provider/Publisher computer has sufficient resources available to launch task.
| |
| − |
| |
| − | ==2.3.Postconditions==
| |
| − |
| |
| − | *1.New metadata records are added to the dataset catalog.
| |
| − | *2.Existing metadata records are updated or deleted from the dataset catalog.
| |
| − |
| |
| − | ==2.4.Normal Flow==
| |
| − |
| |
| − | Two publishing options exist within GOS for publishing a single metadata record to the dataset catalog. Registered publishers can fill out a basic online form to create metadata and publish to the dataset catalog, or publishers can utilize the upload metadata form to publish to the dataset catalog.
| |
| − |
| |
| − | *1.The Data Provider adds ESIP to the keyword list within the metadata record.
| |
| − | *2.The Data Provider submits the publishing request using either the create metadata form or upload metadata form.
| |
| − | *3.The metadata record is validated to ensure it meets the minimum FGDC and ISO requirements established by GOS.
| |
| − | *4.The metadata record is then categorized into a resource content type.
| |
| − | *5.Once a record has been categorized, it is published to the GOS dataset catalog.
| |
| − | *6.The record is then reviewed by the GOS Administrator. If the record is approved it will become viewable and searchable within the portal.
| |
| − | *7.The Data Provider can update and delete records from the dataset catalog with the metadata management tools available to the Data Provider within GOS.
| |
| − |
| |
| − | ==2.5.Alternative Flows==
| |
| − |
| |
| − | One publishing option exists within GOS for publishing multiple metadata records to the dataset catalog. Registered users can batch publish records by registering a catalog of metadata for harvesting. GOS will harvest the catalog at a predefined interval using one of five GOS harvesting protocols. The harvested records will automatically be published to the dataset catalog and approved. If the record already exists within the portal the newly harvested record will replace it.
| |
| − |
| |
| − | ==2.6.Exceptions==
| |
| − |
| |
| − | *1.Records fail to publish due to a validation error. The system will generate a report specifying the reason/description for the failure.
| |
| − | *2.The resource content type must be defined within the metadata record in order for the record to be properly categorized. A domain of valid resource type values is available for ISO and FGDC standards. For FGDC the content type is defined in the XML tag identified by the following XPath expression: /metadata/distinfo/resdesc. For ISO records the XPath expression is as follows: /metadata/distInfo/distributor/distorTran/onLineSrc/orDesc.
| |
| − | *3.Records are not approved. The GOS Administrator will contact the Data Provider to explain the reason for the record not being approved.
| |
| − | *4.The record being published is determined to be a duplicate record. The system should return a message to the user specifying that the record already exists within the portal.
| |
| − |
| |
| − | ==2.7.Extension Points==
| |
| − |
| |
| − | *1. Harvesting
| |
| − | *2. Publishing
| |
| − |
| |
| − | ==2.8.Priority==
| |
| − |
| |
| − | High
| |
| − |
| |
| − | ==2.9.Frequency of Use==
| |
| − |
| |
| − | 1-5 times per user session
| |
| − |
| |
| − | ==2.10.Business Rules==
| |
| − |
| |
| − | List any business rules that influence this use case.
| |
| − |
| |
| − | ==2.11.Special Requirements==
| |
| − |
| |
| − | Identify any additional requirements, such as nonfunctional requirements, for the use case that may need to be addressed during design or implementation. These may include performance requirements or other quality attributes.
| |
| − |
| |
| − | ==2.12.Assumptions==
| |
| − |
| |
| − | The collection level metadata for EIE will be held in GeoSpatial One-Stop (GOS), at least initially. GOS, therefore, controls many actions related to catalog management. Any GOS user that registers as a Publisher can publish metadata to GOS.
| |
| − |
| |
| − | ==2.13.Notes==
| |
| − |
| |
| − | ==2.14.Issues==
| |
| − |
| |
| − | Standards: what metadata standards are going to be supported by EIE? How will these be enforced?
| |
