| Table of Contents | ||||
|---|---|---|---|---|
|
...
Buttons are used to upload a dataset.
...
...
4.3 Input fields
Input fields are the white boxes where information can or must be entered by you. The description with the input field states what information should or can be entered. Input fields that are required to have a value can be recognised by an asterisk*.
...
Invalid or missing entries will result in an error message to be displayed below or next to the input field.
...
4.4 Page Indicators
Page indicators are shown at the top of the page.They behave as tab headers: clicking on an orb will navigate to the corresponding page. The number of page indicators can vary depending on your use of the Sandbox.
The active page is shaded orange with a yellow border (in the image below, the “Upload Dataset” is the active page). This is also indicated by the page title above to the left of the orbs.
...
There are page indicators for the following pages (from left to rightgoing clockwise from the orange item):
Upload Dataset
Track Dataset
Problem Patterns – dataset overview
Problem Patterns – record report
Tier calculations – record report
...
The “track a new dataset” link takes you to the corresponding page.
...
The view detail links open up a popup that displays the details of an error.
...
Links can be greyed when required information is missing. The image below shows that the Track and Issues links are greyed out because there is no information in the input field left of the links.
...
...
4.6 Drop down menus
Dropdown menus allow you to make a selection of a list of predetermined values.
...
...
5 The Basics: arriving at the Metis Sandbox
...
This screen allows you to start accessing the Metis Sandbox functionality. Here you can track an existing dataset, request information about a record within that dataset or create a new dataset. It looks like this:
...
A. Page Indicator: indicates that "Track Dataset Processing" is the current step. Once other steps become available then clicking this will return you to this step.
B. Dataset Id Input: used to enter the id of a previously uploaded dataset.
C. Record Id Input: used to enter the id of a record within the specified dataset. It enables when a dataset id is entered.
D. Create New Dataset Link: enables and navigates to the “Upload a new Dataset” functionality (see below).
E. Track link. This link enables when a dataset id is entered and, when clicked, takes you to the “Track Dataset Processing” functionality (see below) for the dataset with this dataset id.
F. Issues (Overview) link. This link enables when a dataset id is entered and, when clicked, takes you to the “Problem Patterns” functionality (see below) for the dataset with this dataset id.
G. Issues (Record) link. This link enables when a record id is entered and, when clicked, takes you to the “Problem Patterns” functionality (see below) for the record with this record id.
H. Tier Report link. This link enables when a record id is entered and, when clicked, takes you to the “Record Report” functionality (see below) for the record with this record id.
...
The “Upload Dataset” view looks like this:.
...
A. Step Indicator: indicates that "Upload Database" is the current step. If you switch to another step then clicking this will return you to this step.
B. The dataset name input field. A dataset name is valid if it contains only letters, digits and the underscore character (‘_’).
C. The dataset country drop-down.
D. The dataset language drop-down.
E. The harvest protocol radio button set.
F. The zip file input. This appears because “file upload” is the selected protocol. If the selected protocol is changed to “OAI-PMH upload” or “HTTP upload” then an alternative field (or set of fields) will appear here.
G. Step size field.
H. An (optional) checkbox to specify that you want the Metis Sandbox Server to transform your dataset using XSLT. If selected then a file input will appear below it allowing you to upload an XSL file.
I. The “Submit” button: enables when all the (obligatory) fields have been completed.
J. Step Indicator (inactive): clicking this will take you to the “Track Dataset Processing” step.
Enter a descriptive name for your dataset in the input field below “Name”. Only letters, digits and the underscore character (‘_’) are supported. You can select the country and language of the dataset with the dropdown menus.
...
To use the harvest protocol to OAI-PMH, you should enter values for the harvest URL, the metadata format, and optionally a value for Setspec.
...
6.2.3 Upload a file on a server through HTTP or HTTPS
You can also upload a zip file that is accessible with a url. Set the harvest protocol to “HTTP upload” to be able to enter a value for the Url. The url should be the (HTTP or HTTPS) download location of the zip file that contains the dataset records.
...
6.3 XSL Transformation to EDM (Optional)
It is possible to transform the records in the dataset to the EDM format, using XSLT before any further processing. Check the checkmark before “Records are not provided in the EDM (external) format”. An additional file input will appear for an XSL file to be specified.
...
6.4 The step size
This field allows you to influence the sampling behaviour.
...
A submitted dataset id will bring up the track dataset processing view. It will also change the page’s url to reflect the id of the dataset processing being displayed. The dataset processing view looks like the picture below.
...
A. The dataset name. The tick after the dataset name indicates that processing is complete
B. An (optional) flag indicating whether the dataset was xsl-transformed.
C. The processing date, preceded by an (optional) flag indicating that not all records in the dataset were processed.
D. The country and language of the dataset selected when the dataset was uploaded.
E. The processing steps performed on the dataset (they correspond to the list of items just below, element F).
F. The details of the processing steps performed on the dataset.
G. The (optional) warning indicating that not all records in the dataset were processed. See “step size” above for more information.
H. The (not enabled) record id field.
I. The dataset ID of the current dataset.
J. A link to the dataset preview as it would look like on Europeana.
...
The colours of each step indicate how successful this step was:
Green: (success) - the step completed without errors, and all records are considered suitable for ingestion
Yellow: (non-critical warning) - problems with the records have been detected, but the records could still be processed.
Red: (critical warning) - more serious problems with the records have been detected, and (some of) these records could not continue their path through the pipeline. These should longer be considered for ingestion (in their current form).
...
Shown below is an example of a dataset that processed with many errors:
...
A. A link to the errors window
B. The bold font of the number indicates that this is another link to the errors window
C. No report is available for this error, so the the number does not have a bold font and there is no link to the errors window
...
Clicking a link to the errors report will open a pop-up window, allowing you to see the error detail.
...
...
7.4 View the published records
...
You can search for a record using either of these record ids, so the “Report” button will enable itself when any sequence of non-whitespace characters has been entered into the record id field. If, however, the UI detects that you’ve entered an id that matches the format of a valid Europeana record id, then it will show a line connecting the record id with the dataset id, as shown here:
...
A. The record id begins with a slash followed by the dataset id, so the id fields are shown as connected.
B. Both the record id field’s submit buttons (“Tier Report” and “Issues (Record)”) are enabledso the id fields are shown as connected.
B. You can now open the record report by clicking the button labelled “Tier Report”.
...
In the illustration below the computed values are “3” (for the content tier) and “A” (for the metadata tier).
...
A. Page Indicator: the inactive "Track Dataset Processing" orb, indicates that this page is not active and, if clicked, will return the user to the dataset tracking page.
B. The Record Report summary: top-level information about this record as well as record download links.
C. Tier Navigation Orbs: you can toggle between the content and the media tier report from here.
D. Content Tier Information: data about the record's content tier.
E. Media Navigation Orbs: you can navigate multiple media items from here.
F. Processing Errors: record processing error information appears here.
G. Page Indicator: indicates that "Record Report" is the current page (via its orange colour) and that the form below is “clean” (via its tick icon).
...
If there are more than 5 media items available in the record report then the navigation orbs will be replaced with navigation arrows, an editable field and a spinner allowing you to browse the items or jump directly to a specific one, as shown below.
...
...
8.4 Metadata Tier Information
...
Active contextual classes dimension
...
...
9 Problem patterns
You can view problem patterns for both a dataset and for a record. The dataset id and record id fields each have a (secondary) link labelled “Issues”.
...
Clicking “Issues (Overview)”, next to the dataset id input field (A) , will open a problem viewer page for the whole dataset. Clicking “Issues (Record)” (B)will open a problem viewer page for an individual record.
...
The record-references behave as (internal) links to the separate instance of the problem pattern viewer used for records (with the exception of the references for P1, as they are not displayable for individual records).
The problem pattern report can be downloaded using the “export as pdf” link.
The 8 problem patterns that are in use now are:
...
Click on the title of a specific problem pattern to see a description.
...
9.2 Record
The problem pattern viewer for records shows all the types of problem patterns that occur within a single record.
...
Note that two of the page indicators in the image above show the same icon - one for each instance of the problem pattern viewer. The page indicator for problem patterns for a complete Dataset will always appear to the left of the problem pattern of a single record.
If you click on the “</>” button to the right of the problem pattern viewer, a panel expands that provides access to download links for the record.
...