diff --git a/docs/technical-documentation/migrate-csv.md b/docs/technical-documentation/migrate-csv.md index 5238b7269..7a10e890a 100644 --- a/docs/technical-documentation/migrate-csv.md +++ b/docs/technical-documentation/migrate-csv.md @@ -31,7 +31,7 @@ This tutorial uses the configurations and code available in the [migrate_islando Sample CSV and images are also included in the module as a convenience so they are easily available on the Drupal server running the migration. (This is not the recommended method for making files available to Drupal in a real migration.) -The module also contains a Migrate process plugin that transforms strings into associative arrays. This is useful for populating multiple Linked Agent fields. (See "[Typed Relation](../../user-documentation/metadata#typed-relation)" for more information on the Linked Agent field.) It will be available when this module is enabled, and the node migration uses it. It was written generically and will hopefully become part of Migrate Plus, but for now it is here. +The module also contains a Migrate process plugin that transforms strings into associative arrays. This is useful for populating multiple Contributor (field_linked_agent) fields. (See "[Typed Relation](../../user-documentation/metadata#typed-relation)" for more information on the Contributor field's type.) It will be available when this module is enabled, and the node migration uses it. It was written generically and will hopefully become part of Migrate Plus, but for now it is here. When you are ready to create your actual migrations, the contents of this repository can function as a template for you to create the YAML files defining your own migrations. @@ -425,7 +425,7 @@ process: # Iterate over the array of associative arrays. # We create the taxonomy terms here so that we # can specify the bundle - other columns which - # might feed into Linked Agent may contain + # might feed into field_linked_agent may contain # corporate bodies or families. The resulting # array contains the resulting term id (tid) # under the key 'target_id'. @@ -680,7 +680,7 @@ Within `sub_process`, we cannot access the temporary variables or constants that ['target_id' => 44, 'rel_type' => 'relators:pht' ], ] ``` -The final step will be to assign this array to the Linked Agent field. But first, we repeat the process for another column, which contains names that have a different relator, and a different bundle. Finally, we merge the two temporary variables and pass the result to `field_linked_agent`. We don't have to assign the sub-components of `field_linked_agent` here, because this is already the structured data it is looking for. +The final step will be to assign this array to the Contributor field (field_linked_agent). But first, we repeat the process for another column, which contains names that have a different relator, and a different bundle. Finally, we merge the two temporary variables and pass the result to `field_linked_agent`. We don't have to assign the sub-components of `field_linked_agent` here, because this is already the structured data it is looking for. ```yml field_linked_agent: diff --git a/docs/user-documentation/metadata.md b/docs/user-documentation/metadata.md index ec39adeeb..a4f9f5039 100644 --- a/docs/user-documentation/metadata.md +++ b/docs/user-documentation/metadata.md @@ -206,9 +206,9 @@ The Typed Relation field is defined in the *controlled_access_terms* module, is #### Configurations for the Typed Relation field -The Islandora Starter Site includes a Typed Relation field labelled 'Linked Agent' as part of the Repository Item content type, and populates the available relations from the MARC relators list. ![Screenshot of adding a value into a typed relation field](../assets/metadata_typed_relation_field.png) +The Islandora Starter Site includes a Typed Relation field labelled 'Contributors' as part of the Repository Item content type, and populates the available relations from the MARC relators list. This field was formerly called "Linked Agent". ![Screenshot of adding a value into a typed relation field](../assets/metadata_typed_relation_field.png) -The list of available relations for this Linked Agent field is configurable at '/admin/structure/types/manage/islandora_object/fields/node.islandora_object.field_linked_agent'. +The list of available relations for this Contributors field is configurable at '/admin/structure/types/manage/islandora_object/fields/node.islandora_object.field_linked_agent'. !!! islandora "Typed relation tradeoffs" @@ -217,7 +217,7 @@ The list of available relations for this Linked Agent field is configurable at ' Relations are defined in the format *key\|value*, and the key is used in the RDF mapping (see below). -![Screenshot of the 'Available Relations' configuration text box for the 'Linked Agent' field.](../assets/metadata_available_relations_config.png) +![Screenshot of the 'Available Relations' configuration text box for the 'Contributor' field.](../assets/metadata_available_relations_config.png) By default, facets can be created for typed relation fields that will facet based on the linked entity alone, not separating references based on the relationship type. diff --git a/docs/user-documentation/metadata_harvesting.md b/docs/user-documentation/metadata_harvesting.md index 907335cc4..9e74911ff 100644 --- a/docs/user-documentation/metadata_harvesting.md +++ b/docs/user-documentation/metadata_harvesting.md @@ -33,7 +33,7 @@ However, - any field mappings that are not part of the Dublin Core namespace will be filtered out. - any field mappings using Dublin Core Terms (e.g. http://purl.org/dc/terms/extent) will be mapped to their Dublin Core Elements equivalents (e.g. http://purl.org/dc/elements/1.1/format) -- the ability to vary the mappings in Linked Agent fields by relationship, used in JSON-LD mappings to Blazegraph and Fedora, is not available. If you want to expose data in a Linked Agent field to OAI-PMH, you must provide a DC mapping for that field in the RDF mapping. By default, the Repository Item RDF mapping does not include a mapping for the Linked Agent field. +- the ability to vary the mappings in [Typed Relation](../../user-documentation/metadata#typed-relation) fields by relationship, used in JSON-LD mappings to Blazegraph and Fedora, is not available. If you want to expose data in a Typed Relation field to OAI-PMH, you must provide a DC mapping for that field in the RDF mapping. By default, the Repository Item RDF mapping does not include a mapping for the Contributors field (field_linked_agent). !!! tip "Field values not showing up in OAI-DC record?"