-
Notifications
You must be signed in to change notification settings - Fork 6
User Flows
This is the a crucial user workflow - adding an entry to W3ACT. In the prototype, this is a single page form, but in this version, we need to break the workflow down.
- Look up a URI.
- If appropriate, add a new entry.
The user starts by looking up the URL of interest. This gives a status check, and allows the user to decide whether they need to create an entry for this item.
Here is an example from the current prototype:
http://www.webarchive.org.uk/act/websites/url-search?url=http%3A//www.bbc.co.uk/news/
This page allows the user to look up a URL in a way that is compatible with a bookmarklet or other RESTful services.
From here, they can find out:
- If the URI, or a closely related URI (e.g. same domain), already has an entry in ACT.
- If the URI has been crawled (hook into Monitrix - see Data sources).
- If the URI is available from any of the Wayback instances (i.e. hooks to Wayback API - see Data sources).
What this page should also do, but does not do yet:
- Tell you if the URI automatically falls in scope for crawling, or whether additional permissions will be needed.
- Tell you if the URI is held in other archives, a la http://www.webarchive.org.uk/mementos/search/http://www.bbc.co.uk/news/
This uses the same form as the entry editor (below). However, the URL is passed in and should appear in the, and a number of other parameters should also be set.
- Title, pulled from page.
- Legal Deposit Status
- Ends with .uk
- GeoIP settings to be looked up.
TBC
The same form is used to add or edit entries (aiming to avoid user confusion), but some fields may not be edited after they have been added.
In the prototype, this was one long form. In the new version, this should be simplified as much as possible, and use tabbed and/or collapsible sections.
This highest priority is to establish the license to crawl, i.e. whether this is covered by Legal Deposit, and/or whether we have (or wish to request) explicit permission to crawl the site.
TBA
Individual Instances of a Target are annotated in order to QA them and in order to add them to Collections.
TBA