Creating Relationships Between Items
There are three ways to link between items in the database. You can either link components in the same record together (e.g. a jpg image of a document and its transcription in a pdf file) or you can link individual rows in a dataset to another component in the same record. There are two ways to do this, all three methods are described below.
Sometimes it is necessary or desirable to relate components together, for instance if a transcription of a document is loaded along with the digitised image of the same page. Here the two components are the same intellectual content, but presented in different formats. These are therefore related by the ‘Is format of’ relationship. However there are a number of other types of relationship.<ref>Dublin Core Metadata definitions</ref>:
- Is part of: The described component is a part of the referenced component;
- Is format of: The described Component is the same intellectual content of the referenced Component, but presented in another format.
- Is referenced by: The described Component is referenced, cited, or otherwise pointed to by the referenced Component.
- Is replaced by: The described Component is supplanted, displaced, or superseded by the referenced Component.
- Is required by: The described Component is required by the referenced Component, either physically or logically.
- Is version of: The described Component is a version, edition, or adaptation of the referenced Component. Changes in version imply substantive changes in content rather than differences in format.
When you create a relationship between two Components (which have to be in the same Record) the system will put a button on each page so that the user can navigate between the two. You can specify the label to be put on each button so that they accurately specify the nature of the relationship.
Creating a Component Relationship
A Component Relationship is a relationship between two components in their entirety. For example an entire dataset and a document containing the images of the original source from which the dataset was transcribed. IF you want to create a link from individual records (rows) within a dataset, then use the Field Relationship below.
Relationships can be created in two different ways.
- From the Record detail view: In the Component list click on the Admin menu next to the Component you want to add a Relationship to (see screenshot above).
- From the Component admin menu: If you are currently viewing the Component, then the admin menu at the top right of the screen will allow you to create a Relationship.
Linking Between Rows in a Dataset and External Files
If you want each entry in a dataset to link to a different document/file then you need to use this mechanism. For example if you have a list of people buried in a cemetery in a dataset, and you have images of all the monuments in separate files, then each row in the dataset will need to link to a different image.
NOTE: A constraint of this mechanism is that the files and the dataset must exist within the same record.
To do this include a column in the dataset csv file for the file names of the corresponding image. E.g. Test.csv contains:
John, Smith, 1898, Delhi, johnsmithstomb.jpg Fred, Bloggs, 1899, Simla, cemeteryplan.doc
cemeteryplan.doc are loaded as files into the same Record as Test.csv then Frontis will provide a link to the file in the Detail page.
When you import the csv file, the field containing the filename must be classified as Internal File Reference.
See also: Bulk file uploads
Linking Between Rows in a Dataset and another Dataset
Sometimes it is desirable to link a Detail in one dataset to a Detail or group of Details in another dataset. For instance each entry in a dataset containing a list of Census households needs a link to the dataset which lists all the individuals appearing in that Census. This is called a Field Relationship and we can link the Household with a particular 'ID' in the first dataset to the individuals in the second dataset from that household and which also have the same 'ID'.
In order to do this you need to choose the Add Field Link option from the dataset menu which will open the Add Field Relationship screen.
The field relationship creates a link between 2 fields in 2 different dataset components. The system will create buttons which link between the two datasets and will allow navigation between records where specified fields have identical values.
For example one dataset has details of all voyages of ships from a port, another has a list of all individuals which departed from that port on all ships. The field relationship will link the ship with the individuals allowing easy navigation between all individuals on a specific voyage and the details for that voyage.
The Field relationship screen is split into two halves, the left-hand side allows you to specify the 'source' dataset, and the right-hand side the 'target' dataset.
The Source dataset should already be specified since this is the one whose menu you used to open the screen. A dropdown allows you to choose the field in the dataset which will contain the values that will be used to search the target dataset.
The Target dataset is specified on the right-hand side of the screen. A constraint of this is that the two datasets must exist in the same Record.
There are two edit boxes, one on each side of the screen, which allow you to specify the labels which will appear in the forward and reverse buttons that allow the user to navigate between the two datasets. There will be a button on each item's page which the user clicks on to navigate to the other item. Examples are:
- Forward Label: Click to view the individuals on this ship
- Reverse Label: Click to view the ship this individual embarked on
If a label is left blank, then the component name and type will be used as the label. For example:
- Forward: Transcription of Individuals (dataset)
- Reverse: Lists of Ships (dataset)
The following mechanism is NOT recommended, since the IDs of items is not guaranteed to remain the same as the Frontis system evolves.
The only possible way to do it, is to add the HTML into the dataset field which would create a link to the dataset. You could do this manually for each Detail within Frontis, or create a new column in the Excel table and enter the values there then import.
<a href='http://yoursite.com/aps_browse_sources.php?mode=browse_dataset&id=999&s_id=999'> Cemetery File </a>
will appear in the Detail as:
In case you are not familiar with HTML the code above has the following form:
<a href='some url'>TEXT</a>
<a ...> - An 'Anchor' opening tag. An anchor essentially is a link, and the text between the opening and closing tags will be underlined and will be clickable.
href='some url' - A Hypertext REFerence 'attribute' within the Anchor opening tag (i.e. between the <a and >). This is the address that the user will go to when they click on the link. In our case Copy and Paste the URL from the address bar when looking at the dataset in question.
TEXT - The text which you want to be the underlined link. I put Cemetery File, but you could put anything, like 'Click here to view the monumental inscriptions'.
</a> - The Anchor closing tag. This will mark the extent of the underlining.
See also: HTML Documentation
However, please bear in mind that this mechanism does not come with any guarantee, as in the future the URL may change - for instance if the site address changes.