Streamline & clarify the process for exporting and overlaying a Symphony record with a Sinopia description

[NancyL]

Type of change
a request for new workflow

Example RDF records
Please provide URIs or RDF of the bf:Instance. If providing RDF, Turtle is preferred.
https://api.stage.sinopia.io/resource/879212bf-f815-489f-abc5-b9882d74fb12

Resource template
Which resource template does this apply to? In which Sinopia environment (development, stage, production)?

pcc:bf2:Monograph:Instance

Currently, to overlay a Symphony MARC record with a Sinopia description, the cataloger must:

1. Retrieve the Symphony record control number

2. Create a local adminmetadata description for the instance containing that record control number

3. In the relevant instance description, click on export

4. This is a rather slow process. It seems to me that it would be better if it were combined with the export process to create a new Symphony record and in which the local adminmetadata description is machine-created. In this model, the cataloger would:

5. Retrieve the Symphony record control number

6. In the relevant instance description, click on export

7. A box (or something) would pop up in which the cataloger would enter the record control number if overlaying or simply click on "ok" if not

8. The description would be converted to MARC, a local adminmetadata description created as with an export for creating a new record (but with the control number in it), and the record sent to Symphony

This would reduce export to a single process and be much more efficient.

[jermnelson]

I think this issue should be moved to Sinopia Editor