-
Notifications
You must be signed in to change notification settings - Fork 6
App structure
Sam Walton edited this page Jun 12, 2020
·
3 revisions
The Wikilink app has a structure which broadly reflects the way access is provided in The Wikipedia Library, but is in many ways generalised to support other use cases. There are a number of interlocking models which are laid out in the following way.
- Programs group organisations to collate data from all of them in one place. The Wikipedia Library is an example of a program - it has many partner organisations and staff want to view data totals collated from all participating organisations.
- Organisations potentially hold multiple collections with different URL patterns to track, but ultimately have a desire to view all that data in one place. For The Wikipedia Library, organisations are the publisher partners who want to view link tracking data just for their URL patterns in one place. Organisations can be part of multiple programs.
- Collections are usually individual websites or resources published by or of interest to an organisation. For example, Springer Nature hosts both Springer Link and Nature. Collections are tied to a single organisation and organisations can have one or multiple collections.
-
URL patterns define which URLs we track. This data does not need to be in a 'sensible' URL form - we expect a pattern of the form
website.com
to check against. Subdomains and paths are also permitted, such asgateway.proquest.com/openurl/
. A URLPattern is only linked to a single Collection, but a Collection can have multiple URL Patterns. This is helpful, for example, if a website's URL changes but we still want to track changes to both the new and old URLs.