Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-626

API for exchange of Usage Data

    Details

    • Type: New Feature
    • Status: Volunteer Needed (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: DSpace API
    • Labels:
      None
    • Attachments:
      1
    • Comments:
      16
    • Documentation Status:
      Needed

      Description

      Exchange of usage data from a repository to a central server using OpenURL Context Objects via OAI-PMH or SUSHI

      http://wiki.surffoundation.nl/display/standards/KE+Usage+Statistics+Guidelines
      http://wiki.surffoundation.nl/display/standards/info-eu-repo

      The big stakeholders (OA Statistik, PIRUS, SURF, ...) agreed on a standard for exchange of usage data. This could be a very relevant standard to integrate.

        Attachments

          Issue Links

            Activity

            Hide
            grahamtriggs Graham Triggs added a comment -

            I'll add to this that the COUNTER Code of Practice 4 calls for the use of SUSHI:

            http://www.projectcounter.org/r4/COPR4.pdf

            "COUNTER usage reports must also be provided in XML format in accordance with the COUNTER XML schema that is specified by SUSHI ... COUNTER reports in XML must be downloadable using the SUSHI protocol"

            Show
            grahamtriggs Graham Triggs added a comment - I'll add to this that the COUNTER Code of Practice 4 calls for the use of SUSHI: http://www.projectcounter.org/r4/COPR4.pdf "COUNTER usage reports must also be provided in XML format in accordance with the COUNTER XML schema that is specified by SUSHI ... COUNTER reports in XML must be downloadable using the SUSHI protocol"
            Hide
            bram Bram Luyten (@mire) added a comment -

            This is still relevant and alive.

            The SUSHI standard has just been revised by NISO:
            http://www.niso.org/news/pr/view?item_key=2895fae13f1068deb6b405161a9f27a0ecff1d56

            http://www.niso.org/workrooms/sushi/

            Show
            bram Bram Luyten (@mire) added a comment - This is still relevant and alive. The SUSHI standard has just been revised by NISO: http://www.niso.org/news/pr/view?item_key=2895fae13f1068deb6b405161a9f27a0ecff1d56 http://www.niso.org/workrooms/sushi/
            Hide
            joaomelo João Melo added a comment -

            I am planning to contribute/help/improve with a implementation of SUSHI + COUNTER. Just want to check if there is anyone already working on it/interested in it.

            Show
            joaomelo João Melo added a comment - I am planning to contribute/help/improve with a implementation of SUSHI + COUNTER. Just want to check if there is anyone already working on it/interested in it.
            Hide
            joaomelo João Melo added a comment - - edited

            Just adding here my thoughts on the matter.

            OAI-PMH is an excellent protocol for exchanging persistently uniquely identified digital objects. It allows external systems to keep track of changes (because records are uniquely identified), get only the delta ('from' parameter), it is server-side performant (in the sense that it allows one paginate through the results) and so on.

            However, when it comes to usage statistics, trying to embed such data inside the OAI-PMH protocol, which was not created for the purpose, will result in subsequent hacks to keep 3rd party systems correctly synchronised/consistent. Due to the nature of the data, usage statistics is not a good example to apply OAI-PMH. The simple fact that there is no need to have uniquely identified events (might really be overkilling) makes almost all the OAI-PMH arguments fell.

            So, in my point of view, COUNTER + SUSHI fits the purpose a lot better.

            Show
            joaomelo João Melo added a comment - - edited Just adding here my thoughts on the matter. OAI-PMH is an excellent protocol for exchanging persistently uniquely identified digital objects. It allows external systems to keep track of changes (because records are uniquely identified), get only the delta ('from' parameter), it is server-side performant (in the sense that it allows one paginate through the results) and so on. However, when it comes to usage statistics, trying to embed such data inside the OAI-PMH protocol, which was not created for the purpose, will result in subsequent hacks to keep 3rd party systems correctly synchronised/consistent. Due to the nature of the data, usage statistics is not a good example to apply OAI-PMH. The simple fact that there is no need to have uniquely identified events (might really be overkilling) makes almost all the OAI-PMH arguments fell. So, in my point of view, COUNTER + SUSHI fits the purpose a lot better.
            Hide
            robintaylor Robin Taylor added a comment -

            I've attached a very old IRUS-UK patch supplied by @Mire. This should not be applied, its only provided as an example of code that exports COUNTER compliant stats. @Mire are developing an updated patch for version 5 which could be used as the basis for a more generic COUNTER stats development.

            Show
            robintaylor Robin Taylor added a comment - I've attached a very old IRUS-UK patch supplied by @Mire. This should not be applied, its only provided as an example of code that exports COUNTER compliant stats. @Mire are developing an updated patch for version 5 which could be used as the basis for a more generic COUNTER stats development.

              People

              • Assignee:
                Unassigned
                Reporter:
                bram Bram Luyten (@mire)
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated: