...
KE is a co-operative effort between JISC, SURF, DEFF and DFG. International interoperability guidelines for the comparable exchange of usage data is one of these co-operative efforts.
Section | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Whereas these three projects all make use of the OpenURL Context Object standard, some subtle differences have emerged in the way in which this standard is actually used. Nevertheless, it is important to ensure that statistics are produced in exactly the same manner, since, otherwise, it would be impossible to compare metrics produced by different projects. With the support of Knowledge Exchange , a collaborative initiative for leading national science organisations in Europe, an initiative was started to align the technical specifications of these various projects. This document is a first proposal for international guidelines for the accumulation and the exchange of usage data. The proposal is based on a careful comparison of the technical specifications that have been developed by these three projects.
...
Note |
---|
please put a reference to the PIRUS1 outcome, and write a little more details about the three scenario's envisioned by PIRUS1 |
...
...
4. Data format
To be able to compare usage data from different repositories, the data needs to be available in a uniform format. This section will provide specifications for the aspects of the usage event that need to be recorded. In addition, guidelines need to be developed for the format in which this information can be expressed. Following recommendations from MESUR and the JISC Usage Statistics Project, it will be stipulated that usage events need to be serialized in XML using the data format that is specified in the OpenURL Context Objects schema. The XML Schema for XML Context Objects can be accessed at http://www.openurl.info/registry/docs/info:ofi/fmt:xml:xsd:ctx. The specifications for the use of OpenURL ContextObject in this section are more restrictive than the original schema with respect to the occurrence and the permitted values of elements and attributes.
...
Description | The country from which the request originated may also be provided explicitly. |
XPath | ctx:context-object/ctx:requester/ctx:metadata-by-val/ctx:metadata/?dcterms:spatial |
Usage | Optional |
Format | A two-letter code in lower case, following the ISO 3166-1-alpha-2 standard. http://www.iso.org/iso/english_country_names_and_code_elements |
Example | ne |
...
Description | The full HTTP user agent string |
XPath | ctx:context-object/ctx:requester/ctx:metadata/dini:requesterinfo/dini:classification/dini:user-agent |
Usage | Optional |
Format | String |
Example | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) |
4.3 Legal issues
Usage of IP addresses and the protection of a 'natural person'
The IP address of the requester is pseudonymised using encryptions, before it is exchanged and taken outside the web-server to another location. Therefore individual users can be recognised when aggregated from distributed repositories, but cannot be referred back to a 'natural person'. This method may seem consisted with the European Act for Protection of Personal data. The summary can be found here: ?http://europa.eu/legislation_summaries/information_society/l14012_en.htm. Further legal research needs to be done if this method is sufficient to protect the personal data of a 'natural person', in order to operate within the boundaries of the law.
5. Transfer Protocols
5.1. OAI-PMH
5. Transfer Protocols
5.1. OAI-PMH
The data exchange between a data provider and a log aggregator may be based on the widely established OAI Protocol for Metadata Harvesting (OAI-PMH). OAI-PMH was originally designed for the exchange of document metadata. Thus, this standard is mainly adapted in a specific The data exchange between a data provider and a log aggregator may be based on the widely established OAI Protocol for Metadata Harvesting (OAI-PMH). OAI-PMH was originally designed for the exchange of document metadata. Thus, this standard is mainly adapted in a specific way of handling a certain kind of metadata, as usage data does not meet the general requirements of typical formats used.
In principle, the protocol specifies a data synchronisation mechanism which supports a reliable implementation of one-way data synchronisation. This functionality also fits well for the purpose of usage data transfer.
...
- The current version of the list can be reached by placing /current/ in the local path of the URI, e.g.: http://purl.org/robotslist/current/robotlist.xml
- An overview of the previous versions can be found by going to the parent of the /current/ localpath element, e.g.: http://purl.org/robotslist/
- Previous versions of the robot list can referred to by using the preferred date instead of the /current/ local path element, e.g.:http://purl.org/robotslist/2010/05/12/robotlist.xml
Info |
---|
To be done: find a web location; create a "cool" URI, implement the above mechanism |
- of the /current/ localpath element, e.g.: http://purl.org/robotslist/
- Previous versions of the robot list can referred to by using the preferred date instead of the /current/ local path element, e.g.:http://purl.org/robotslist/2010/05/12/robotlist.xml
Info |
---|
To be done: find a web location; create a "cool" URI, implement the above mechanism |
Note |
---|
Knowledge Exchange is offering a web-location; the PURL has been requested by OCLC. The next steps are to put the list online, and make a PURL reference. |
7. Legal boundaries
7.1. Usage of IP addresses and the protection of a 'natural person'
The IP address of the requester is pseudonymised using encryptions, before it is exchanged and taken outside the web-server to another location. Therefore individual users can be recognised when aggregated from distributed repositories, but cannot be referred back to a 'natural person'. This method may seem consisted with the European Act for Protection of Personal data. The summary can be found here: ?http://europa.eu/legislation_summaries/information_society/l14012_en.htm. Further legal research needs to be done if this method is sufficient to protect the personal data of a 'natural person', in order to operate within the boundaries of the law.
Info |
---|
In these guidelines the IP addresses are pseudonymized using MD5 hash encryption |
Note |
Knowledge Exchange is offering a web-location; the PURL has been requested by OCLC. The next steps are to put the list online, and make a PURL reference. |
Appendix
Code Block | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
<?xml version="1.0" encoding="UTF-8"?> <context-objects xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dcterms="http://dublincore.org/documents/2008/01/14/dcmi-terms/" xmlns:sv="info:ofi/fmt:xml:xsd:sch_svc" xsi:schemaLocation="info:ofi/fmt:xml:xsd:ctx [http://www.openurl.info/registry/docs/info:ofi/fmt:xml:xsd:ctx]" xmlns="info:ofi/fmt:xml:xsd:ctx"> <context-object timestamp="2009-07-29T08:15:46+01:00" identifier="b06c0444f37249a0a8f748d3b823ef2a"> <referent> <identifier>https://openaccess.leidenuniv.nl/bitstream/1887/12100/1/Thesis.pdf</identifier> <identifier>http://hdl.handle.net/1887/12100</identifier> </referent> <referring-entity> <identifier>http://www.google.nl/search?hl=nl&q=beleidsregels+artikel+4%3A84&meta="</identifier> <identifier>info:sid/google</identifier> </referring-entity> <requester> <metadata-by-val> <format>http://dini.de/namespace/oas-requesterinfo</format> <metadata> <requesterinfo xmlns="http://dini.de/namespace/oas-requesterinfo"> <hashed-ip>b505e629c508bdcfbf2a774df596123dd001cee172dae5519660b6014056f53a</hashed-ip> <hashed-c>d001cee172dae5519660b6014056f5346d05e629c508bdcfbf2a774df596123d</hashed-c> <hostname>uni-saarland.de</hostname> <classification>institutional</classification> <hashed-session>660b14056f5346d0</hashed-session> <user-agent>mozilla/5.0 (windows; u; windows nt 5.1; de; rv:1.8.1.1) gecko/20061204</user-agent> </requesterinfo> </metadata> </metadata-by-val> </requester> <service-type> <metadata-by-val> <format>http://dublincore.org/documents/2008/01/14/dcmi-terms/</format> <metadata> <dcterms:format>objectFile</dcterms:format> </metadata> </metadata-by-val> </service-type> <resolver> <identifier>http://www.worldcat.org/libraries/53238</identifier> </resolver> <referrer> <identifier>info:sid/dlib.org:dlib</identifier> </referrer> </context-object> </context-objects> |
...