Inside the record editing window, fields in bold red type are mandatory fields, which must be filled in order for the new record to be saved. There are range of options for editing both the record and also change the structure of the record (**Modify Structure** in the top left corner). It is not recommended to modify the structure of records unless you are an experienced user and have a good reason for doing so. In the bottom banner, there are several options for saving the current new record and then taking other actions:
- - - duplicating the record (Dupe), - creating a fresh new record (New), - save the current record but remain editing it (Save), - save the current record and close it (Save + Close), - and close the current record without saving it (Drop Changes). ### 2.2 Permission settings You can control and change permissions settings to all the data entry of a specific record type by clicking on \[Permission settings\] at the top of the list (right-hand panel below) which pops up on rollover of \[New\], or by clicking on \[Settings\] below \[New\] button. It offers additional controls over the new record parameters:  By default, records in a new database will be visible only to logged in users. \[Settings / Permission settings\] brings up a dialogue allowing you to control the type and permission settings for future additions (cf. [chapter 2 Roles and permission](https://heurist-doc.huma-num.fr/_Dbs8brPTN-jiWtrYzEaaQ#Roles-and-Permissions)). This can be used not only to determine the future record type and permissions which will be created when you click on \[New\], but also provides a URL which can be bookmarked or added to a web page to create new records with those specific permissions. The use of a tag or tags can be used to flag new records added, for example, by guests, that can be retrieved for editorial vetting. Other values can also be set with suitable parameters in the URL.  ## 3. Upload Files ### 3.1 Delimited text / CSV #### 3.1.1 Presentation **Delimited text / CSV** upload is the primary means for populating your database with bulk data. This tool is used to parse delimited text, comma-separated or tab-separated variable (CSV or TSV) data, and then organise that data into structures that are compatible with Heurist. The import tool is a very powerful way to populate your database, but it can be a complex process. It is important that the data is as clean as possible, prior to import. If you are unsure about any step in the import process, please consult the Heurist Help System, watch the walkthrough video, or contact Heurist community mailing list. There are three ways to begin using the **Delimited texte/CSV** upload workflow: - Upload new file -- an existing CSV or TSV file from your desktop - Select previously uploaded file -- these files appear in a dropdown menu - Paste delimited data below -- you can paste data directly from the clipboard. Please observe the conventions for representing data, including using column labels in the first line, proper line terminations, quotes, and special symbols. These are explained in the help sidebar, and also in a dedicated page in the Help System. #### 3.1.2 What is CSV? CSV, which stands for 'comma seperated values', is a simple text-based format for saving spreadsheets or tables. Data is stored as text. Each line in the text file represents a row of data, and commas are used to seperate each column (hence 'comma-seperated'). Consider the below example. You may have a text file called `actors.csv`, which looks as follows: ``` Surname, First Name, Street, Suburb, Postcode Chopra, Priyanka, 200 Malabar Cres, West Bandra, 400050 Weaving, Hugo, 65 George St, Sydney, 2000 ``` If you opened this file in a spreasheet program such as Excel, Numbers or Sheets, it might look like this:| **Surname** | **First Name** | **Street** | **Suburb** | **Postcode** |
|---|---|---|---|---|
| Chopra | Priyanka | 200 Malabar Cres | West Bandra | 400050 |
| Weaving | Hugo | 65 George St | Sydney | 2000 |
At a minimum, you must have a suitable record type structure defined in the database (it is possible to add addiitonal fields durign the import, but you at least need th record types and their connections) and a corresponding CSV/TSV file holding the entries you wish to transform into records.
Importing can be a complex business. It is important to clean up the data as much as possible in advance. The following provides some tips on how to prepare your data:
- We recommend breaking very large files into manageable blocks of about two thousand lines. - Only one record type can be imported at each step of the process. - Have one row per entry, with each column containing a single element of data (split concatenated values into separate columns, and place notes about data items in a separate column, not appended to the data value). - The first line MUST contain column labels. Do it for your own sanity! The first line of your data also determines the expected field count. - Data rows must occupy a single line of data terminated with a linefeed: CRLF (Windows) or LF (Unix/Mac). Linefeeds within memo fields should be represented by CR only. Fields should be separated by tab or comma. Quotes may exist within unquoted fields, but within quoted fields they should be preceded by a backslash ( \\" ). Fields containing the field separator should be enclosed in quotes. Editors such as [Notepad++](http://notepad-plus-plus.org/%22%20%5Ct%20%22_blank) (a free, open source Windows application) show tabs, CR and LF as symbols and can do global replacements on them. - Coded columns should use a consistent set of codes. In addition to your spreadsheet program, you may find OpenRefine a useful tool for checking and correcting coded columns, splitting fields, georeferencing, finding URL references and so on. - We strongly suggest editing the structure of the database to add any fields and terms that you will require for the import, before attempting to load the data. If you start trying to load data without the appropriate fields in place you will find it frustrating having to exit the process repeatedly to add fields. - If you have missing data for **Required fields**, you may find it convenient to set those fields to **Optional** before importing, then set them back to **Required**, then use **Database > Structure > Verify** to get a list of the records which need correcting. Alternatively, you can add some dummy value to the data, such as 'Missing', and search for this value after import. - The import process can be repeated on the file to extract multiple entities from different columns and replace them with record IDs which can be used in a subsequent insertion or update of records. - Please visit the page on [Importing delimited text files](http://heuristnetwork.org/importing-data/) on the Heurist network site for tips on successful import. <ce renvoi ne devrait plus être nécessaire par la suite> #### 3.1.5 Delimited Text Importer Wizard The Import Wizard takes you through a number of screens and steps to assist you in defining the import. (Read the screen instructions carefully. It might be a good idea to carry out a trial import with a small dataset to check that the result is as you expected.) ##### Set Data Source These options are: - **Select uploaded file**. If you are importing a file you have imported before, select it from the dropdown. To clear this list, click \[Clear All files\]. - **Upload File**. If you are importing a new file, select it using the \[Upload File\] button. - **Paste Data**. If you wish to use copied delimited text, paste it in the box below and click \[Upload Data\]. ##### Set Import Parameters For CSV files, before carrying out the import, you can set the import parameters (these settings are saved) as follows: - **Encoding**. Select the appropriate encoding. - **Field Separator**. Select the appropriate field separator: Comma or Tab. - **Fields Enclosed In**. Select the appropriate field enclosure: (', " or None). - **Line Separator**. Leave as **Auto-Detect** or select the appropriate line separator: Windows, Unix or Mac. - **Multi-value separator**. Select the appropriate multi-value separator: (e.g. | ; : /). - **Date Format**. Select the appropriate date format: European (dd/mm/yyyy or US (mm/dd/yyyy). Other date formats are possible and will be handled in the following wizard dialog.) Click \[Analyse Data\] again to parse the expected results. This checks that the structure of your data matches what the Import Wizard expects. The header of the upload CSV (the first line of your data determines the expected field count) is checked against your import parameters, column names are extracted and encoding verified. The Import Wizard then attempts to convert the file based on your settings and displays the result (the expected input as rows (records) and columns (fields)). Review the result and any error messages and update the source data if required. If you don't have Heurist Record ID (H-ID) value in your file, click on \[Continue\], else, specify the record that must be used to match the H-ID with already existing data. :::info In this section you can also select any input column that contain dates (dd-mm-yyyy, mm-dd-yyyy or Iso standard) -- this allows the data to be parsed to extract consistency formatted date fields. ::: Once it's done click on \[Continue\]. ##### Select Primary Record Type and Dependencies The primary record type is the one represented by each row of the input file. Additional record types may be imported from selected columns prior to import of the primary, as determined by the dependencies shown. The creation of the primary record type from rows in the input file depends on the prior identification of other entities which will be connected via pointer fields or relationships. The tree below shows the dependencies of the primary record type determined from its pointer and relationship marker fields. Where an input entity matches an existing record, its ID value will be recorded in an ID field which can be used subsequently as a pointer field value; where no existing record is matched a new record is created and the new ID recorded. Check record types to be imported. Red indicates required pointer field.  #### 3.1.6 The three importing steps When the CSV/TSV data are loaded and that the record and connected entities are selected the import interface will take you through 3 important steps in order to correctly match and prepare your data for import: 1. **Matching** step which take care of verifying if data imported already exists inside the database and thus triggering the appropriate action (updating, deleting, etc.). 2. **Fields to import** step which define which columns of the imported CSV file will be imported into the database and in order to populate which field in the selected record type. 3. **Insert/update** step which take care of populating or updating the database given the chosen scenario. ##### Step 1. Matching In the first step of the matching process you can choose what to match or to skip matching. Select a radio button: - **Match on CSV Columns**. To match import rows against existing records,select at least one Matching key column (later you can select for mapping) and ensure all selected key columns are allocated to a field. You can check (and scroll through) a sample of the field data to be mapped in the Values column. A new identification field will be created. [](https://docs.heuristref.net/uploads/images/gallery/2026-07/dmqimage.png)Matching sets this ID field for existing records and allows the creation of new records for unmatched rows.
- **Use Heurist ID column**. (Only usable if H-ID column exists both in the CSV file and in the records to update inside heurist). In this case, the identification H-ID field (which is a field managed by the system) will be used. - **Skip Matching** (all new records). Skips the matching step (in this case only new records are created, one per input row).Select the \[Match on Columns\] / Skip Matching button\] (depending on the three previous cases). Matches are shown.
##### Step 2. Fields to ImportIf all existing rows already match existing records (e.g. you may have already carried out the import successfully), then you can select the displayed Skip Update button to cancel the import.
The **Import Summary** box shows a mapping summary: - **Existing**. Number of matching records (that already exist based on selected matching columns). These will therefore be skipped. - **New**. Number of input rows for which no matching record has been found. These will therefore be added. The following options are for matched or new rows: - **Show**. This displays the records on screen (click the Close (x) button). - **Download**. This downloads the records to a CSV text file.The three matching, importing and inserting steps can work as an iterative operation if the spreadsheet data you are importing is a complex one. Therefore the import workflow allows you to progressively import columns which identify subsidiary entities (other Record Types linked through Record Pointers to the main record type you want to update or need to create data into) such as Place, Organisation, Collection, Series, Person, etc. The first step is to match identifying key fields and create new records from unmatched rows. The process starts with record pointers first and once all subsidiary entities have been matched and imported, you can import the primary entity type selected in the previous import phase.
- Record IDs for the imported columns are added as column 1. Copy and save these data immediately if there are additional fields to import, to allow use of the record IDs as record pointers. Warning: you will lose the record IDs as soon as you start over, so save the data below to a file first. <!--TODO Vincent: je ne comprends pas bien ce que cette partie signifie --> - If the displayed results are not what you expected, then go through the steps again (go back a step or click \[Back to Start\] if you wish to start again; all of your settings will be lost) and make any adjustments (including adjustments to the CSV or TSV file and/or **Record Type**). Complete the **Column to Field Mapping**. Since new records are to be created, make sure you select all relevant columns; all **Required fields** must be mapped to a dedicated CSV column in order to proceed further. Click \[Prepare\] when ready (importing does not happen yet). A message will appear if you haven't selected any fields other than the ones which are used to match records, so those are the only fields which will be set, and the result may be incomplete records. Click Proceed if you wish to continue, otherwise Cancel and review your settings.
##### Step 3. Insert/Update In this step you carry out the update (this will update the database based on your settings so be sure this is what you wish to do). Select an option on how you wish to treat data that already exists in a field: - Retain existing values and append distinct new data as multiple field values (existing values are not duplicated) - Add new data only if field is empty (new data ignored for non-empty fields) - Add and replace all existing value(s) for the record with new data If you are happy to proceed with the import, click \[Start Inset/Update\]. You will be notified of the updates: Click \[OK\] and close the window to exit the Import wizard. Review the imported records.  ### 3.2 Zotero Bibliography **Zotero Bibliography Sync** allows you to automatically synchronise a Zotero web library with the already existing bibliography structure within Heurist. It is especially powerful because it allows you to update bibliographic data from an active Zotero library, thereby saving time and effort in updating bibliography records within Heurist.The synchronisation function looks for changes made since the last synchronisation, so it works fast even with a 20,000+ Zotero library once the initial synch has been done (which will take half an hour or so).
Heurist provides the following functions and capabilities for importing bibliographic data: - Automatic identification and disambiguation of imported bibliographic types. - Authors stored as person records allowing rich complementary data. - Series, Journals, Publishers stored as separate records to eliminate data redundancy. - Pre-defined domain profiles with collections of useful references, tags and searches. To use the **Bibliography Sync function**, you first need to define a connection to a Zotero Library in `Design/properties/Synchronisation and Indexing`. If this has not yet been done, in your database, you will be prompted to edit the settings that establishing such a Zotero connection. The relevant field is Zotero web library key(s) and IDs for synchronisation.It should be noted that not all the zotero fields are synchronised with heurist bibliography record types. Moreover the synchronisation process will create automaticaly new records for Persons (author), organizations (Publisher), Places (publication location) and of course book references and so on. The Synchronisation is a one way process from a given Zotero collection to a Heurist database.
### 3.3 Heurist XML / JSON #### 3.3.1 Summary **Heurist XML / JSON** allows data to be imported from an XML or JSON format that is specially tailored for compatibility with Heurist. When preparing data in this format, it is strongly recommended to first download the XML template. This is an XML document, following a Heurist-XML(HML) schema, that presents the core definitions of records that are necessary for proper functioning of your database. Following this template, you can design an XML document that can be easily read by Heurist. Once an HML or JSon-format is ready, select the file to upload from your desktop. Doing this takes you to a screen where the data is parsed and check. This screen enumerates the records to be imported and asks for final confirmation before the data is imported to create new records. Click **\[Import Records\]** to start the import.Contrary to the CSV/TSV import which allows a very refined way of updating or creating given field values with the use of [matching and preparing steps](#Import-Records-from-CSVTSV), the XML/JSON import is a one time operation that imports a whole set of contents in one go. If the data is correctly formatted, as when exported from one Heurist database, it is a very fast and accurate way of importing data into another Heurist database (it can even download structure to accomodate the data provided the source database is a Registered database).
#### 3.3.2 Import XML/JSON Heurist will import HML exported from another Heurist database or from an external source which have been converted to HML format. ##### For Heurist database sources Unless the source database structure is identical with the target, it should be registered first on the heurist master server which keep an index of unique identifiers for record type and fields in order to reuse it yourself or to be shared with other heurist users. You can register your database by going to **\[Design > Register\]**. Registration thus allows the target database to contact the source Heurist database in order to import (or update) the record (entity) type and field definitions it finds in the HML file, as well as permitting the inclusion of global conceptIDs in the HML. For HML exported from a Heurist database, **<database id=??>** is normally set to indicate the source database. If it is set, synchronisation of definitions will be performed before the data are imported. ##### For non-Heurist database sources To import a file generated from another source, eg. by transformation of an RDBMS to XML: - the XML file should conform to the template output from the target database using **\[Import > Download XML template\]**; - the target database must contain definitions for all the record (entity) types and fields encountered in the XML file (in other words, only entity type and field codes defined in the XML template should appear); - the XML file should specify a Heurist database ID of 0 . If a database ID is specified, synchronisation of definitions from that database will be performed before the data are imported. Since imported files will normally use a template for record types and fields exported from the target database, this is only useful for synchronising vocabularies and terms. Record (entity) types and fields can then be specified using concept IDs (these will have a database ID of zero followed by the local ID (eg. 0-1234) for record types or fields defined locally in an unregistered target database. Terms in the incoming data can be specified in one of the following ways which are evaluated in order: - first it looks for a valid local term ID. - If that is not found it tries to match it as a concept ID. - It then looks for an alphanumeric term applicable to the current field, and finally a **standard code** applicable to the current field. - If it gets to the end without finding a match, the value will be added to the database in the (first) vocabulary used by the field. ##### The XML Template To create and import an XML file eg. to transfer data from another non-Heurist file or database, we strongly recommend using the XML tempalte which can be exported from Heurist using **\[Populate > Download template (XML)\]**. The template file contains full instructions for setting up the file. However, it is worth explaining the handling of record pointer fields in a little more detail. To reference an existing record in the target database, the record number must be prefixed with H-ID- otherwise Heurist interprets the number as any identifier that matches the identifier filled in <id> for another record in the import file, which may therefore be numeric or alpah/numeric. This behaviour is quite intentional precisely to avoid making false connections (record IDs are database specific and cannot be known in advance unless re-exported and re imported, which is rendered unnecessary by our approach).Note that inside the XML template, RECORD\_REFERENCE may be replaced with a numeric or alphanumeric reference to another record, indicated by the <ID> tag. Note that this reference will be replaced with an automatically generated numeric Heurist record ID (H-ID), which will be different from the reference supplied. The reference supplied will be recorded in a field Original ID.
If you wish to specify existing Heurist records in the target database as the target (value) of a Record Pointer field, specify their Heurist record ID (H-ID) in the form H-ID-nnnn, where nnnn is the H-ID of the target record in the target database. Specifying non-existent record IDs will throw an error. The record type of target records are not checked on import; pointers to records of the\* wrong type can be found later with **\[Admin > Verify integrity\]**. Example: I put in H-ID-2456 for a record pointer value: - if there is a record "2456", the record pointer is set to point to record "2456" - if there is no record "2456", it is reported as an error - if I put in any other type of value for the record pointer value eg. 2456 or wxyz or CallNo123456, it will look for a record defined in the XML with the value "2456" or "wxyz" or "CallNo123456" respectively, and set the record pointer value to the H-ID assigned to this record. It will not try to second guess that "2456" is a valid record pointer value, because that is so database specific as to be almost certain to fail if there is no record with th especified ID, an error will be reported ::: ### 3.4 KML #### 3.4.1 Introduction **KML** is designed specifically for the import of bulk geospatial data into Heurist. In order to use this tool, first prepare a KML document in the standard format. Note that popular mapping tools such as Google Earth and Google Maps are able to natively export geospatial data in KML format. #### 3.4.2 Import KML KML (Keyhole Markup Language) is a file format used to display geographic data in an Earth browser such as Google Earth, Google Maps, and Google Maps for mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. All tags are case-sensitive and must be appear exactly as they are listed in the KML Reference. The Reference indicates which tags are optional. Within a given element, tags must appear in the order shown in the Reference. Heurist will recognise the KML format and process the file, and prompt you for a record type. All records created by a single KML import will have the same record type. 1. Select **\[Choose File\]** and browse to select a KML file to import. 2. Click **\[Continue\]**. A summary of records to be imported is shown. When ready, click **\[Continue\]**. Heurist will recognise the KML format and process the file, and prompt you for a record type. 3. Select the record type and click Continue.All records created by a single KML import have the same record type
### 4 Media Files - images, videos, audio and other files #### 4.1 Upload media files / images **Upload media files/images** function, is designed for use by **Database Managers** only. It allows you to upload media files/images directly onto the Heurist server for use with a particular database. There are a range of allowable file formats/extension that can be uploaded in bulk in this way. As a Database Manager, you can select a media/upload folder in the relevant directory on the Heurist server. After selecting the target folder within this directory, Add Files from the desktop to upload. Once selected, click **Start uploads** to begin the process of copying these media files onto the Heurist server. Once completed, close the pane by clicking **Finished**. #### 4.2 Upload media from URL **Upload media from URLs** function, is designed for use by **Datab**a**se Managers** only, uploads a set of files specified by URLs, directly in the database. You can paste URLs and optional description in the area, CSV format is recommended. After pasting URLs or uploading CSV file, the URLs are checked and if the media files are supported, uploaded to the Heurist database. After uploading, assign each file to a record type and link it to the appropriate database entry by selecting file assignment.  #### 4.3 Index external files **Index external files** function, which is reserved for **advanced users** only, scans media folders and add missed to Media Files. Files have to be uploaded through Populate either using : - Function **Upload media files/images** - or by direct sftp access to the file\_uploads directory (or sub-directories) on the server for larger files. Make sure the format of the extensions is supported by Heurist. Then, select the folders to scan. Click on **\[Proceed\]**. #### 4.4 Create media records **Create media records** function, is designed for **Database Managers** only, and is reserved for **advanced users**. It creates, updates and reads XML manifest files in the folders listed in *Design > Properties* and creates Digital Media records for all files uploaded to the database. Before, make sure to upload files through Populate (**Upload media files/images**). And make sure that the format of the extensions to scan is supported by Heurist. Click on "Continue" to synchronize the files. #### 4.5 IIIF Images IIF (International Image Interoperability Format) provides a standard for image interchange widely used by museums, art galleries and others in the GLAM sector. To enter an IIIF image, you need a **File or Media URL** field, when editing a specific record, enter the path of either: - a IIIF image with an url ending /info.json - a IIIF manifest with a name like manifest.json Heurist will recognise these specific IIIF file and display them by using the embedded IIIF [Mirador Viewer](https://projectmirador.org/). #### 4.6 Process IIIF Manifests **Process IIIF Manifests** function, is reserved for **advanced users.** It reads IIIF manifests and incluiding Annoftations, and creates or updates Annotation records in the Heurist database. [](https://docs.heuristref.net/uploads/images/gallery/2026-07/Dglimage.png) TODO: need more comprehensive documentaiton ### 5 Annexes #### 5.1 CSV Import Tips and Notes #### 5.1.1 Importing child records Let's assume we have a Person **Record Type** with **Child records** linked fields such as Birth, Death, Life Event, Address association, etc. To import Address Association - which associates a Person with a Place for a particular date, date range or list of years - you must import Places to create Place **H-IDs**. But you must also import Persons to create Person **H-IDs**.This may be tricky because the child pointer to these records may be a required field. But it needs to be done first in order to be able to create the child records.
#### 5.1.2 Beware matching a repeating value... Beware matching on a value which repeats as it can result in a new record for every value. For example, Address Association might be derived from a file listing an address for a particular person for each of 20 years in 20 rows. So one may have 10 rows with *17, First Street* and 10 rows with *35, Second Avenue*, and each of those rows has a different value in the year column. What you want is TWO records, each with 10 years listed in a repeating YEAR field, not 20 records each with a year value and each address repeated in ten records. You should therefore ONLY match on Address (and Person). If you match on Year you will end up with 20 records, each with one year value, rather than 2 records, each with 10 year values. #### 5.1.3 Importing child records **Child records** can be used to describe inherent and strongly dependent components of an entity, for example scenes in a frieze or painting, motifs in a scene, features of a building, worked edges on an artefact. They can equally be used to group rarely used attributes specific to a particular variant of an entity, for example pottery attributes for archaeological finds (where some finds are pottery, others bone, glass, stone or shell) - this is the case used here to illustrate the import of child records. After defining all the fields for the **Child Record type**, you need a CSV file which either references the **H-ID** of the parent records, or a unique field or combination of fields in the parent records. In our case the *Finds* were imported from an **Access** database and the *Find ID* in the source database is included as *Artefact ID*. This allows it to be matched with *Finds.Artefact ID (Access DB)* in Heurist to obtain the parent **Record Pointer**. The attributes to be imported into the child record will also be defined in the file. For categorised fields (a controlled list), we will use Heurist's Term List field type which may be represented in teh incoming data either as the labels or as the codes (foreign keys) used to reference the lookup tables in the source. @TODO : check images on the previous paragrap in sharedocs document To illustrate, let's define a test field *Pottery type* field with values "One", "Two" and "Three", which have numerical code 1, 2 and 3 respectively: Here is the very simple test file imported by way of illustration.Note that we use the code rather than the label (where exporting data from another software you may get either out of an SQL query depending on the way it is structured. In MSAccess, for example, some fields get joined with their lookup tables automatically and give you the label. Other softwares just give you the actual Foreign Key value in the field)
``` Artefact ID, Pottery type 244415, 3 ``` This file is loaded using **\[Import > Delimited text (CSV/TSV)\]**. First, we select the **Parent record type** (which is called *Finds* in this test case) as the target entity type and carry out matching using a unique field or combination (Artefact ID in this case) in order to create the Heurist IDs for the parent records (Finds), either through finding an existing record and setting its ID or creating a new one and assigning a new ID. This step can be skipped if the file contains Heurist IDs for the parent records:  Once you've done that, change target to the child record type (Pottery information in this case) and match on a combination of fields which uniquely identifies each child record (these fields may include the parent record ID, that is Find H-ID in this case). Then select the field(s) you want to import (which ++must++ include the parent record ID, as this determines the parent appropriate to each child record):  In the data entry form for the record imported you will see the child record link (in this case we have not yet defined the full set of fields for the child record, nor the constructed title mask):  The child record identifies its parent and also shows the imported field(s). Notice that I imported "3" and it came out as the label "Three". That is NOT because Heurist connects numbers with their textual representation but because Heurist will look for the standard code if it does not find a matching label. If neither the label nor the code is recognised for one or more rows of incoming data, Heurist offers you the opportunity of adding unknown labels.  #### 5.1.4 Importing relationships / markers People often ask "How can I import a relationship marker". The short answer is "you can't" since relationship markers are just markers (and constraints) and contain no data. The long answer is, you don't import relationship markers, you import **relationship records**. ##### Importing relationship records from a CSV file While relationships can be imported from an XML file, the easiest way is to create a CSV file containing the relationships, and import using the CSV importer. This minimally contains something to identify the source record (eg. names or the Heurist ID) and the target record, adn the type of relationship. Dates and other attributes eg. notes or bibliographic references or degree of certainty, can also be provided. ``` Source Name, Source First name, Relation type, Target Last name, Target First name , Start date, End date \ Dupond, Michel, is husband of, Dupont, Anne, 1512, 1531\ Dupont, Bernadette, is wife of, Dupond, Jean,,\ etc. ```The direction in which the relationship is defined does not matter provided the right term is used. Relationship type can either be directional, as in the case of isChildOf and isParentOf, or non-directional eg. isRelatedTo
Use **\[Import > Delimited (CSV/TSV)\]**: Identify the target record type as Relationship record.Relationship records might be marked as a hidden record type, in which case they will not show up in the options. Go to Design > Record types and set them as visible.
Match on the two source columns (*Source Name* and *Source First Name* in this case, or other columns that will identify the source record, for example the ID or title etc.), then a match on the two target columns. This will create appropriate Heurist ID columns (if the Heurist IDs are already in the file these can be selected). Set the generated Heurist IDs to match the Source and Target record pointers, and the relationship type to match the relationship type field. Finally, import the data into the **Relationship records**. The imported relationship records will appear in any relationship markers whose constraints they fit. Note: Relationship Markers do not contain any data. Nothing! These are markers that have two functions: - Show **Relationship records** that match the marker (type of source, type of target, type of relationship) - Show where you want to create relationships and constrain possible relationships (target type (s), relationship types) If you put a **Relationship Marker** in the source type records, and another in the target type records, and if the relationships are either non-directional eg. isRelatedTo (applies in both directions) or the inverse of one-another (eg isChildOf and isParentOf), the relation will show in both records with the appropriate terms, for example:  ### 5.2 Detailed mapping and use of KML and spatial data #### 5.2.1 KML Field Definitions This table shows how the data is mapped into Heurist; it lists the KML tags that Heurist recognises as record details, and the bibliographic data fields that they are imported to.Contact the Heurist Network Association for the full list of KML Field Definitions for the XML file to determine how the data is mapped into Heurist.
Heurist attempts to import each <Placemark> as a separate record.| KML tag | Heurist detail field |
|---|---|
| <name> | Title (detail type #160) |
| <address> | Location (#181) |
| <AddressDetails> | |
| <phoneNumber> | Contact information (#309) |
| <TimeSpan><begin> | Start Date (#177) |
| <TimeSpan><end> | End Date (#178) |
| <TimeStamp><when> | Date (#166) |
| <Region> | Geographic object (#230) |
| <Point> | |
| <LineString> | |
| <LinearRing> | |
| <Polygon> | |
| <MultiGeometry> | |
| <Snippet> | Shared scratchpad |
| <description> | |
| <Metadata> |
| Feature | Annotation overlay | Full manifest management |
|---|---|---|
| Supported source Manifest version | v3 only | v2 and v3 |
| Source Manifest ownership | External provider / registered file | Imported into Heurist management |
| Generated Manifest output | Source v3 Manifest with Heurist AnnotationPage links when requested through the IIIF API | Heurist managed v3 output |
| Canvas list ownership | External provider | Heurist |
| Canvas identifiers | Original source Canvas URIs | Heurist Canvas API URLs |
| Canvas records created | No | Yes |
| Annotation records created | Yes | Yes |
| Manifest metadata editable in Heurist | No managed Manifest record is created | Yes, used in generated output |
| Best use | Add Heurist annotations to an existing v3 Manifest without creating a Manifest record | Build or take over a Manifest in Heurist |
| **Omeka S** | **Heurist** |
|---|---|
| Resource\_class | defRecTypes |
| Resource\_template\_property | defRecTypeStructure (order, altlabel, requirements and data\_type?) |
| Property | defDetailTypes |
| Resource | Records |
| Value | recDetails |
| **Property ID** | **Table Name** | **Vocab Name** | **Resource Class ID** |
|---|---|---|---|
| 202 | fonctions | fonctions | 155 |
| "223,245,325" | pays | pays | |
| 283 | causes-fin-brevets | brevet cause fin | |
| 291 | genres | genres | |
| 329 | types-adresses | types de adresses | |
| 346 | typesdeproces | types de proces | |
| "290,383" | roles | roles |
| **rty** | **id** | **local\_name** | **dty\_Type** | **dty\_ID** | **ptr/vocab Explanation** |
|---|---|---|---|---|---|
| 7 | date | date | 9 | ||
| 252 | birthdate | date | |||
| 35 | isReferencedBy | blocktext | |||
| 131 | nick | freetext | |||
| 95,110,111 | 143 | surname | freetext | 1 | map property 143 to heurist 1 for classes 95.. |
| 150 | 143 | surname | resource | 16 | map property 143 to heurist 16 for class 150 |
| 230 | parrain | resource | 95 | ||
| 125 | gender | enum | 20 | ||
| 202 | agent | enum | 6255 |