Access to Memory (AtoM)

I think handling the addition of relationship terms by the CSV would likely be too complicated and, if possible, we should require that they be added before an import is done (in the web UI terms and their converse can be defined... or they can be set to be reciprocal).

I ended up, in the PR for #13286, renaming the "sourceAuthorizedFormOfName" and "targetAuthorizedFormOfName" columns to "objectAuthorizedFormOfName" and another "subjectAuthorizedFormOfName" (given that "source" and "target" don't really make sense as column names). By defining an object and a subject this means that only one form of a relation type can be used in the "relationType" column (previously named "category").

Here's a list of applicable types, excluding reciprocal types, derived from an SQL query (maybe we should add an option to the authority relationship import task to display these relationship names):

mysql> select ti.name from relation r inner join term_i18n ti on r.object_id=ti.id where r.type_id=177 and ti.culture='en' and r.object_id != r.subject_id;
+-----------------------+
| name                  |
+-----------------------+
| is the superior of    |
| controls              |
| is the owner of       |
| is the predecessor of |
| is the parent of      |
| is the grandparent of |
| is the provider of    |
+-----------------------+

Here's, as an alternative, a list of relations going in the other direction.

mysql> select ti.name from relation r inner join term_i18n ti on r.subject_id=ti.id where r.type_id=177 and ti.culture='en' and r.object_id != r.subject_id;
+-----------------------+
| name                  |
+-----------------------+
| is the subordinate of |
| is controlled by      |
| is owned by           |
| is the successor of   |
| is the child of       |
| is the grandchild of  |
| is the client of      |
+-----------------------+

Re: the above comment... we could dynamically create a list of allowed relation types (so any types added by the user get included), including both reciprocal types and ones with converse relation types, and display that in the command "long help" (./symfony help csv:authority-relation-import).

Actually relation import currently works for relationship types like "is controlled by" if you simply reverse the placement of the authority names in the "objectAuthorizedFormOfName" and "subjectAuthorizedFormOfName" columns so it works as expected. In general "objectAuthorizedFormOfName" is __ of/by "subjectAuthorizedFormOfName" works.

If we need to provide an automated way of importing relationship types probably supporting this via our SKOS import, if it's not already supported (doesn't look like it is for SKOS export but it might be for import), would be the way to go.

Sounds good!

I'll make these fixes (should only take a few hours, if that):

• Make unknown relationship type simply skip the row with a warning
• Make relationship matching case insensitive
• Fix naming of export columns

Fixed.

One subtask remaining: https://projects.artefactual.com/issues/13329

php symfony csv:authority-export /path/to/file

php symfony csv:authority-relation-import --index /path/to/file