Usage processing Product Specification

[kjgarza]

Purpose

This is a new product specification. To review go to Files changed and click Display the rich Diff

closes: https://github.com/datacite/tasks/issues/69

Types of changes

• [x] New feature (non-breaking change which adds functionality)

• [ ] Breaking change (feature that would cause existing functionality to change)

• [ ] New Product (non-breaking change which adds a new service)

Reviewer, please remember to:

• Be humble in the language and feedback you give, ask don't tell.
• Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
• Ensure you give reasons for the changes you are proposing.

[kjgarza]

@sarala I made further changes based on the product validation session, mostly on three areas:

1. Enable multiple and unintrusive ways to detect the DOI on the landing page. This is would ease the installation of the code without much development needed.
2. A deactivation flow, from when the user decides to drop the service
3. URL-DOI check to discard counts from when the code is posted on the wrong landing page.

[kjgarza]

some were worried about not being able to execute javascript.

I think this refers to the fact that machines/API's cannot execute the JS tracker, this is true but that is a limititation of the general approach In the grant. There were also comments about user disabling JS, and that's fine, we cannot force users to be tracked.

Do we foresee any security issues with using 3rd party tracking?

Not really, we are the only third-party tracking here and the fact of including the tracking on the page is that the repo wants to be tracked. The source code is open as well and the users can see what we are doing if they so wish.