Changes between Version 8 and Version 9 of VirtualCollectionRegistry/Help
- Timestamp:
- 08/04/14 12:59:23 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
VirtualCollectionRegistry/Help
v8 v9 2 2 3 3 extensional:: Type of virtual collection that explicitly enumerates the references to resources or metadata documents that make up the collection 4 intensional:: Type of virtual collection that defines a query by which the items of the collection can be retrieved from a secondary service (experimental, use at own risk!)4 intensional:: Type of virtual collection that defines a query by which the items of the collection can be retrieved ad-hoc from a secondary service (experimental, use at own risk!) 5 5 6 6 purpose:: An indication of the intended usage of the present virtual collection 7 research:: The virtual collection bundles resources that are relevant to a specific research (question). 8 reference:: The virtual collection bundles resources, that are to be cited in a publication. 9 sample:: This virtual collection bundles is intended to serve as an sample for research data 10 future-use:: (Actually, this is more a placeholder, e.g. people are unsure, what their VC may become. Before publishing, they should select one of the the above. Or, if required, we'll need to add more purposes). 7 11 8 12 reproducibility:: An indication of the degree to which results obtained from processing of the present collection can be expected to be stable … … 10 14 fluctuating reproducibility:: Processing results may vary 11 15 untended reproducibility:: No claims with respect to the stability of the processing results are made 12 reproduc ability note:: Optional notes describing the expected reproducibility of processing results in more detail16 reproducibility note:: Optional notes describing the expected reproducibility of processing results in more detail 13 17 14 18 keyword:: A word or short phrase signifying a salient facet of the present virtual collection 15 19 16 creators:: [Guidance note] Add a creator for each person involved in the creation of this virtual collection20 creators:: One or more persons, who created this virtual collection. \\ [Guidance note] Add a creator for each person involved in the creation of this virtual collection 17 21 18 resources:: [Guidance note] Click 'add' to add an individual reference of the type 'Metadata' or 'Resource' and optionally add a label and/or description. Click 'add more' to add multiple references (one per line) of one type without labels or resources. Individual resources can be edited at any stage.22 resources:: A persistent reference to the members that make up this virtual collection. These members may be of type ''metadata'' for referencing metadata or ''resource'' for directly referencing a resource. \\ [Guidance note] Click 'add' to add an individual reference of the type 'Metadata' or 'Resource' and optionally add a label and/or description. Click 'add more' to add multiple references (one per line) of one type without labels or resources. Individual resources can be edited at any stage. 19 23 20 [query] description:: Prose description of the procedure by which the collection items can be retrieved from the external service 21 [query] URI:: Location or identifier of the service from which the items should be retrieved 22 query profile:: Identifier of the mechanism by which the items should be retrieved 23 query value:: The value(s) that should be passed on to the service by which it can look up the items that are part of this collection 24 The following are only relevant for ''intensional'' virtual collections 25 [query] description:: A prose description of the procedure by which the collection items can be retrieved from the external service. 26 [query] URI:: The location of the service from which the items should be retrieved. This value may be a persistent identifier, but could also be a plain URI ('''TODO''': Should this always be a PID, because URIs are not sustainable by definition?). Example: In case of FCS this could be the URI of an endpoint or a more enhanced aggregator. 27 query profile:: Identifier of the mechanism, i.e. the protocol to be used, by which the members of the virtual collection should be retrieved. A application exploiting the query can use this to use a proper driver to talk to the service. Example: In case of CLARIN-FCS access the endpoint by FCS-compatible means. 28 query value:: The query that should be passed on to the service by which it can look up the items that are part of this collection. This value should be in the query language supported by the service. Example: In case of CLARIN-FCS, this value is the CQL query to be send to the endpoint.