Skip to content

4. Attributes

Jump to bottom
COUNTERMetrics edited this page May 1, 2024 · 1 revision

Access_Types

The CRD has no attribute for Access_Type: we’re recommending use of the standard R5.1 Access_Type definitions.

R5.1 includes three Access_Types: Controlled, Open and Free_To_Read (described at https://cop5.projectcounter.org/en/5.1/03-specifications/03-counter-report-common-attributes-and-elements.html#access-types). In the context of datasets, we propose utilising the following Access_Type elements:

  • Controlled: describes materials in a controlled access repository - for example where registration is required..
  • Open: describes open access materials, accessible without registration or subscription.Open applies where the report provider asserts that the content is open access, irrespective of the license (that is, a Creative Commons license is not essential), and the content may have been Open from the day of publication, or after expiry of an embargo, but it is not intended to return to Controlled status.
  • Free_To_Read: describes content that is available to all users on this platform, regardless of authorization status, but not Open (e.g. it may return to Controlled status in the future).

Questions for repositories

  1. Do you foresee any significant difficulties for repositories using the R5.1 Access_Type attribute?

Questions for repositories and libraries

  1. Will the inclusion of the Access_Type attribute help you to better report on and understand usage within the repository?

Data_Types

R5.1 includes many more Data_Types than the CRD Dataset.

The CRD includes only one Data_Type, which is Dataset. For data-only repositories, Data_Type=Dataset remains the default. For mixed-content repositories, the full list of COUNTER Data_Types as described in R5.1 at Section 3.3 is available. A mapping between COUNTER Data_Types and the resource types within the DataCite metadata schema is provided below for quick reference, excluding those Data_Types used specifically for databases.

Terms which are the same: Audiovisual, Book, Dataset, Image, Journal, Other, Report, Software, Sound, Standard

Mapped terms (COUNTER Data_Type > DataCite resource type)

  • Article > JournalArticle
  • Book_Segment > BookChapter
  • Conference > ConferenceProceeding
  • Conference_Item > ConferencePaper (Posters could be logged under Other, recordings under Audiovisual)
  • Interactive_Resource > InteractiveResource
  • Multimedia > Other
  • News_Item > Text
  • Newspaper_or_Newsletter > Text
  • Patent > Other
  • Reference_Item > Text
  • Reference_Work > Text
  • Thesis_or_Dissertation > Dissertation
  • Unspecified > Other

Questions for repositories

  1. Does the extended list of Data_Types present any problems for your repository?

Filtering Reports using Attributes

R5.1 requires that report consumers be able to pre-filter Reports by Data_Type and Access_Type in addition to the CRD filters of YOP, Access_Method, and Metric_Type. Similarly, R5.1 allows report consumers to explicitly Include_Parent_Details and Include_Component_Details.

Questions for repositories

  1. Would the additional filters present implementation difficulties for you as a repository manager?

Clone this wiki locally