XSEDE is conducting a review of its metadata-related use cases to clarify our understanding of researchers' needs in regard to research data and metadata.
Prioritized Item | Average Rating | Individual Ratings | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
DM-09: Search metadata for specific objects of interest (Capability Delivery Plan) This use case describes how an individual researcher searches a metadata collection to identify data objects relevant to a given project. The result is a list of identifiers that the researcher can use to retrieve data objects. (This use case does not cover the data access experience: there are several other use cases in the repository that cover data access and data transfer.) Please click the title above to view an overview of this method, then click the "Full description" link to review the use case description. | (3 votes) |
| ||||||||||||||||||
DM-05: Manually create metadata for a data object (Capability Delivery Plan) DM-05, DM-06, and DM-07 describe three ways that researchers create metadata: by hand, via a custom research application, and via automatic extraction. All three cases rely on an identifier for the data object(s) being described. All three can be combined with metadata storage (DM-08) such that the new metadata is immediately added to a collection. Please click the title above to view an overview of this method, then click the "Full description" link to review the use case description. | (3 votes) |
| ||||||||||||||||||
DM-08: Store metadata for later use (Capability Delivery Plan) This use case describes how researchers add metadata to a metadata collection. The collection might be stored locally (for personal use on the researcher's own system) or on a server (with any of the following: high storage capacity, backups, shared use, community curation). This may be combined with any of the three metadata creation use cases (DM-05, DM-06, DM-07) such that new metadata is immediately added to a collection. Please click the title above to view an overview of this method, then click the "Full description" link to review the use case description. | (3 votes) |
| ||||||||||||||||||
DM-10: Add metadata search features to an application (Capability Delivery Plan) Whereas the other use cases in this review describe how individual researchers access a metadata collection, this use case describes a software development experience: specifically, the ability to add metadata search features to an application or science gateway. The purpose is to provide a customized interface and user experience to a specific research community or research project. Please click the title above to view an overview of this method, then click the "Full description" link to review the use case description. | (3 votes) |
| ||||||||||||||||||
DM-06: Run a researcher-supplied tool to generate metadata for data objects (Capability Delivery Plan) DM-05, DM-06, and DM-07 describe three ways that researchers create metadata: by hand, via a custom research application, and via automatic extraction. All three cases rely on an identifier for the data object(s) being described. All three can be combined with metadata storage (DM-08) such that the new metadata is immediately added to a collection. Please click the title above to view an overview of this method, then click the "Full description" link to review the use case description. | (3 votes) |
| ||||||||||||||||||
DM-07: Automatically extract metadata from data objects (Capability Delivery Plan) DM-05, DM-06, and DM-07 describe three ways that researchers create metadata: by hand, via a custom research application, and via automatic extraction. All three cases rely on an identifier for the data object(s) being described. All three can be combined with metadata storage (DM-08) such that the new metadata is immediately added to a collection. Please click the title above to view an overview of this method, then click the "Full description" link to review the use case description. | (3 votes) |
|