...
The user may have arrived at this document through the mediation of a referrer. This is typically a search engine, such as Google or Yahoo.
Wiki Markup
- Who (Identification of user/session)
- What (Item identification)
- Type of request performed (e.g. full-text, front-page, including failed/partially fulfilled requests)
- When (Date and time)
- Usage event ID
In line with these JISC recommendations, it has been decided in the SURF SURE project to provide the following data elements:
...
C-class Subnet | |
Description | The first three bytes of an IP-address, which are used to designate the network ID. It is similar to the IP-address, with the crucial difference that the final (most significant) byte, which designates the HOST ID is replaced with a '0'. |
Usage | Mandatory |
Format | Three decimal numbers separated by a dot, followed by a dot and a '0'. |
Example | 118.94.150.0 |
Geographic location | ||
Description | The country from which the request was | |
Usage | Mandatory | |
Description | The country from which the request was | |
Usage | Mandatory <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fc015db0-c0e5-4d24-b565-b806106ac353"><ac:plain-text-body><![CDATA[ | |
Format | A two-letter code in lower case, following the ISO 3166-1-alpha-2 code.[[2] | http://www.surffoundation.nl/#_ftn2] \ ]] ></ac:plain-text-body></ac:structured-macro> |
Example | ne |
URL of document | |
Description | The document identifier provides a globally unique identification of the resource that is requested. |
Usage | Mandatory |
Format | The identifier must be given in the form of a URL. At the level of the service aggregator, this URL must be connected to the object's URN, so that the associated metadata can be obtained. The URN can be found by retrieving the URL of the object file in the DIDL file that is maintained by KNAW. |
Example | /bitstream/1887/12100/1/Thesis.pdf |
...
- The SURE Statistics project will attempt to restrict its focus to requests which have consciously been initiated by human users. For this reason, automated visits by internet robots must be filtered from the data as much as possible. The Log Aggregator must maintain a file which list the names of internet robots that individual repositories must use during the filtering of their results. The name of this file must indicate its version. The name of the first file that will be published will be robots-v1.xml. Repositories can use the version indication in the filename to check if they are working with the most recent list of internet robots.
- If a single user clicks repeatedly on the same document within the same 24 hours, this should be counted as a single request.
- One single publication may be split into a set different files. The impact of such variations in the organisation of complex objects must be nullified. The consultation of a part should count towards the statistic of the whole. It should make no difference if a publication consists of one pdf-files or of multiple pdf-files.
6. Data formatunmigrated-wiki-markup
In compliance with the JISC Usage Statistics Review, individual usage events need to be serialized in XML using the syntax that is specified in the OpenURL Context Objects schema.\[[3]\|http://www.surffoundation.nl/#_ftn3\] This section will describe a recommended practice for the use of this schema.
The root element of the XML-document must be <context-objects>. It must contain a reference to the official schema and declare two namespaces: xmlns:ctx="info:ofi/fmt:xml:xsd:ctx" and xmlns:dcterms=http://dublincore.org/documents/2008/01/14/dcmi-terms/.
...
Each usage event must be described in a separate <context-object> element, which must appear as a direct child of <context-objects>. Two attributes must be used:
- The time and date on which the usage event took place must be recorded in the timestamp attribute.
- The identification of the usage event must be captured in an attribute with the name identifier.
Within <contextobject>, a number of elements can be used which describe the context of the usage event. The names of these elements are as follows:
- <refererent>: the object that was downloaded or viewed
- <requester> refers to the agent that has initiated the usage event
- <serviceType>: the type of service that was requested
- <referrer>: the system that has forwarded the reader to the downloaded object
- <resolver>: the institution that provides access to the requested item and which has received the usage event.
Information about these contextual entities can be given in four different ways. Firstly, they can be characterised using an <identifier>. Secondly, metadata can be included literally by wrapping these into the file using a <metadata-by-val> element. Thirdly, a reference to metadata stored elsewhere can be included by using <metadata-by-ref>. A fourth method is the use of the element <private-data>. In the SURE Statistics project, only the first two methods shall be used. Listing 1 is an example of a full OpenURL Context Object document.
<?xml version="1.0" encoding="UTF-8"?> |
Listing 1.
- Under <referent>, the two identifiers for the requested document must both be given in separate <identifier> elements.
- Element <referring-entitity> contains information on the referrer. The URL that was received from the referrer and the classification of the search engine, if it was used, must both be given in an <identifier> element.
- The <requester>, the agent who has requested the <refererent> must be identified by providing the C-class Subnet, and the encrypted IP-address must both be given in separate <identifier>s. In addition, the name of the country where the request was initiated must be provided. The <metadata-by-val> element must be used for this purpose. The country must be given in <dcterms:spatial>. The dcterms namespace must be declared in the <format> element as well.
- The DC metadata term "type" is used to clarify whether the usage event involved a download of a object file or a metadata view
...
- .
- Finally, an <identifier> for the institution that provided access to the downloaded document must be given within <resolver>.
----[1
...
- |http://www.surffoundation.nl/#_ftnref1
...
- ]
...
...
...
- |http://www.surffoundation.nl/#_ftnref2
...
- ]
...
...
[
...
...
- |http://www.surffoundation.nl/#_ftnref3
...
- ]
...
- The
...
- XML
...
- Schema
...
- for
...
- XML
...
- Context
...
- Objects
...
- can
...
- be
...
- accessed
...
- at
...
...