Capture Google Sheet ID in the metadata as 'import_source'

[McFateM]

Taking steps to implement this in a PR today. In the case of import directly from a Google Sheet my code may append one or two columns to the headers and every ingested row. This can effectively address issue #20 provided the Google Sheet is NEVER sorted and the row numbers remain unchanged throughout the sheet's life! The two columns are:

• import_source - Contains the ID of the Google Sheeet
• import_index - Contains the row number of the object from the Google Sheet IF no 'import_index' row is otherwise defined.

[DiegoPino]

@McFateM hey. Happens that i also have #20 use case now (well, happens if you need to add a page to a book in a 16000 pages ingest!). So once you have that pull, i can integrate that functionality for CSV/excel also to keep it in sync. Any ideas on how you want to deal with the UI aspect/validation of that? Best!

[McFateM]

I added a comment to #20 with brief explanation of how I implemented this. No changes to the UI in my implementation, but that might be of interest too.

[McFateM]

@DiegoPino Per yesterday's conversation I'm completely re-thinking and re-working this. The goal in our workflow is to capture in our metadata a field that can be used to lead us back to the Google Sheet and row that an object was imported from.

To that end I'm introducing an $imi_import_source_tracking UI element and variable. The UI element will be a text field and enabling check box. The text field will be populated, by default, with a string representing the specified Google Sheet ID (or full URL) with the specified 'range' appended to it. Since this is a text field the user will have the ability to replace the default with whatever they wish. If this text field is enabled (using the corresponding check box), upon ingest the row number of an imported object is appended to the string (the value of $imi_import_source_tracking) and that result is subsequently appended to end of the row's data in a column specifically named 'imi_import_source_tracking'.

My own workflow around this feature provides an element in my Twig template like this...

{# The following MODS extension elements may be specific to Digital Grinnell! #} 
<extension> 
  {% if attribute(data, 'imi_import_source_tracking') %}  
    <dg_importSource>{{ data.imi_import_source_tracking }}</dg_importSource>  
  {% endif %}
</extension> 
``` 
So when engaged, this feature leaves a MODS/extension/imi_import_source_tracking element in each object's record that can be used to determine where the record was imported from.