Install taxonomy terms even if theyre duplicates of terms in another vocabulary.

[rosiel]

Addresses #158

• Adds an id column to the spreadsheet.
• Uses the id column as the ids: token in the migration's .yml definition
• Makes nested terms (in LC Resource types) point to their parent with the parent's id.

[rosiel]

From @mjordan, yes, things could get weird in workbench if you have the same term in two places:

If you are including the term name in your input CSV, with no vocab ID namespace in the term data, wb will use the first one in the View lookup and log that it did that. Working from memory here....

Should we include a disclaimer, that when you're setting up your site, maybe delete one of these two competing Resource Types vocabularies?

[mjordan]

One more point for clarity: if the field references only one vocabulary, Workbench will use that vocabulary ID (from the field's config) to look up the term and will not be aware of identical term names in other vocabs. If the field references multiple vocabs, and the user does not include namespaces, Workbench will complain during --check (and ask you to use namespaces in your input CSV). So things will only get weird if you have a field that references a single vocabulary and that vocabulary contains terms with identical names, or if the field references multiple vocabularies and your CSV includes terms names that are identical but the namespace is the same on the identical names.

[jordandukart]

[notice] Processed 891 items (891 created, 0 updated, 0 failed, 0 ignored) - done with 'islandora_defaults_tags' does as it says.