Closed adam-vessey closed 1 year ago
What steps does it take to reproduce the issue?
Site installation using an --existing-config, with this module enabled.
--existing-config
N/A
Don't recall the exact error, but it will attempt to create the term before the islandora_display taxonomy itself is configured, due to the site installation flow (was encountered previously with islandora_fits when dealing with the islandora-starter-site):
islandora_display
islandora_fits
islandora-starter-site
... looking back at https://github.com/roblib/islandora_fits/issues/12 , I'm not sure there's an explicit error, but just that the term will probably not carry the intended value for field_external_uri, but will instead be left blank.
field_external_uri
Sys admin.
The term to be able to be created without error.
Which version of Islandora are you using?
Any related open or closed issues to this bug report?
Same class of issue as https://github.com/roblib/islandora_fits/pull/14
Screenshots:
I prefer (and seemed to have convinced others?) that we should take all the default config stuff including this term out, and put it in the Starter Site.
What steps does it take to reproduce the issue?
Site installation using an
--existing-config
, with this module enabled.N/A
Don't recall the exact error, but it will attempt to create the term before the
islandora_display
taxonomy itself is configured, due to the site installation flow (was encountered previously withislandora_fits
when dealing with theislandora-starter-site
):... looking back at https://github.com/roblib/islandora_fits/issues/12 , I'm not sure there's an explicit error, but just that the term will probably not carry the intended value for
field_external_uri
, but will instead be left blank.Sys admin.
The term to be able to be created without error.
Which version of Islandora are you using?
N/A
Any related open or closed issues to this bug report?
Same class of issue as https://github.com/roblib/islandora_fits/pull/14
Screenshots: