GEOSS Banner

4.2 Use cases: user quality model

RATINGS

    4.2.1 A rating based on a dataset as a whole

    • User creates one GVQ_FeedbackItem. In this and all subsequent cases, it is assumed that the user is not generating raw XML/JSON, but is generating these entities by filling out a form which allows them to select the dataset from a list or search, and to select /enter other values as appropriate using an easy and interactive interface.

    • The user supplies a rating (numerical score between 1 and 5)

    • The primary target of the GVQ_FeedbackItem which is generated will refer to the data set in question, using a unique identifier (MD_Identifier).

    • User information (as for all subsequent cases) may be attached to the GVQ_FeedbackItem by accessing futher parts of the form, to give varying amounts of detail about the user’s identification, expertise and domain.

    4.2.2 A rating based on a spatial or temporal subset of the data

    This works as described for 4.2.1, except that a data-centric focus is added to the primary target reference. The user would supply this by selecting a spatial and / or temporal region, and specifying any specific spectral bands to which the feedback applies. This combination describes the part of the dataset the feedback is about, by giving a bounding area and/or time frame. If more than one ‘hotspot’ area of interest/concern is being referred to, further focus elements may be added.

    4.2.3 A domain-specific rating in the context of weather forecasting

    This works as described for the rating above, except that the domainURN of the item is http://www.eionet.europa.eu/gemet/concept/9278 - a “weather forecasting” domain focus.

    4.2.4 Justification for a rating

    This involves creating a GVQ_FeedbackItem containing:

    • One rating (this contains a score and a text justification)

    As in the examples above, the GVQ_FeedbackItem should point to the dataset in question as its primary target.


GENERAL FEEDBACK

    4.2.5 Provide general feedback on a complete dataset

    • User creates one GVQ_FeedbackItem

    • The item contains a comment.

    • The primaryTarget of the GVQ_FeedbackItem refers to the data set in question, using a unique identifier (MD_Identifier).

    4.2.6 Provide general feedback on a part of the data

    • As for 6.4.2, one of more data-centric foci should be added to the primary target reference to describe the part of the dataset to which the feedback refers.

                

    4.2.7 Provide general feedback on a metadata record

    • User creates one GVQ_FeedbackItem

    • The item contains a comment.

    • The primaryTarget of the GVQ_FeedbackItem refers to the data set in question, using a unique identifier (MD_Identifier).

    4.2.8 Provide general feedback on a specific metadata record elements

    Again, the user creates one GVQ_FeedbackItem containing a comment, with the metadata document as its primaryTarget. However, this time sufficient detail must be given in the comment to identify the section of the metadata document to which the feedback refers. For an XML document, this may be achieved using xpath.

    4.2.9 Add a domain-specific comment to a data set

    A domainURN which maps to a conceptual dictionary description of the application domain should be supplied, as shown in 4.2.3.

    4.2.10 Start a thematic discussion on a dataset

    This could work like a message board opened by creating a GVQ_FeedbackItem with a subject, but no comment or other content, giving the dataset as primaryTarget. Any replies to this item are seen as posts on the subject.


EXTERNAL FEEDBACK

    4.2.11 Report external feedback related to a dataset

    • User creates one GVQ_FeedbackItem

    • The item contains an externalFeedback element, which locates the external feedback using a resourceURL, and specifies a mime-type which can be used to retrieve the external feedback.

    • The primaryTarget of the GVQ_FeedbackItem refers to the data set in question, using a unique identifier (MD_Identifier).

    4.2.12 Report external feedback related to a part of a dataset

    This works as for 4.2.12, except that one or more data-centric foci should be added to the primaryTarget as described in 4.2.2.

    4.2.13 Report publication which cites a dataset

    • User creates one GVQ_FeedbackItem

    • The item contains a citation element, which locates the publication using details such as ISBN, ISSN, doi, onlineResource URL, and standard citation information such as author and title.

    • The primaryTarget of the GVQ_FeedbackItem refers to the data set in question, using a unique identifier (MD_Identifier).


ADDING PRIMARY, SECONDARY AND SUPPLEMENTARY TARGETS

    4.2.14 Add primary target

    A GVQ_FeedbackItem may be directly applicable to more than one resource. If this is the case, then more than one primaryTarget may be added, each with its own unique identifier.

    4.2.15 Add secondary target

    A GVQ_FeedbackItem on resource A may be not directly applicable to resource B, but it may be very relevant, such that anyone searching for feedback on resource B would benefit from the option of seeing and using the feedback on resource A. An example might be a piece of feedback on an individual Landsat tile which is relevant to all Landsat users, but does not directly apply to the whole Landsat product. In this case, resource B (the generic Landsat dataset) should be added as a secondaryTarget while resource A (the specific Landsat tile) remains the primaryTarget.

    4.2.16 Add supplementary target

    A GVQ_FeedbackItem which references a resource only for illustrative purposes should use supplementaryTarget for that. An example might be a GVQ_FeedbackItem on resource A explaining an error found to be in A. Anticipating the difficulty of discovering and treating the error, the user adds a supplementaryTarget to a dataset B which also had the type of error in an earlier version but it got fixed later by its producer. The producer might want to follow this link to B to help assess the error. It is, however, unlikely that anyone interested in B will want to know about A, and thus a supplementaryTarget is the right choice.


SEARCH

    4.2.17 Search for comments pertaining to a domain

    This would work by first finding a URN within the applicable ontology, e.g. GEMET concepts. Then, all Domains which map to the URN are identified (we might want to include related domains, using some semantic tools) and the GVQ_FeedbackItems which have the matching domainURNs are searched.

                 


<<Prev T.O.C.  Next>>
Tag
none

Files (0)

 
You must login to post a comment.