field_genre in islandora_defaults points to an undefined "genre" taxonomy

[mdlincoln]

As far as I can tell, when field_genre was added to Islandora defaults, it referenced a genre taxonomy. But the taxonomy itself isn't defined in that module. So when we install the module now, we get the field but no taxonomy with it.

[mdlincoln]

I see now this shows up in https://github.com/Islandora/controlled_access_terms/tree/8.x-1.1/modules/controlled_access_terms_defaults/config/install but for some reason it's not getting installed when we try to build ISLE?

[seth-shaw-unlv]

Perhaps you are pulling the 1.0.0 tag?

[seth-shaw-unlv]

Or perhaps you are not enabling the controlled_access_terms_defaults submodule?

[mdlincoln]

I can see the genre taxonomy definition yml file at codebase/web/modules/contrib/controlled_access_terms/modules/controlled_access_terms_defaults/config/install/taxonomy.vocabulary.genre.yml

Trying to run drush en controlled_access_terms or drush en controlled_access_terms_defaults just returns a message that both modules are already enabled, and doesn't seem to add the Genre taxonomy.

[hachacha]

I just tried uninstalling and reinstalling then running the drush cim to see what the config looks like and it's suggesting that this field should be deleted.
So does that imply that it's always being deleted when trying to install? Should it be exported first?

[seth-shaw-unlv]

Uninstalling controlled_access_terms_defaults won't purge the configs. (It is designed to be enabled once and then disabled, leaving the configs behind, like search_api_solr_defaults.) The best way to manage missing configs is to export your configs (drush cex -y), copy the missing configs into config/sync, and then re-importing them (drush cim -y).

[kspurgin]

Same issue @mdlincoln is reporting was in the sandbox @dannylamb set up for MIG use.

I didn't realize the genre taxonomy was set up outside islandora_defaults, so I set up that taxonomy in islandora_defaults in the config changes that came out of the MIG sprint.

Danny has those config changes, but they haven't been merged anywhere. But just noting that there is now a duplicate genre taxonomy defined in my changes. There were a couple other entity reference fields that were supposed to be pulling from a taxonomy that didn't exist in the sandbox, so I defined those taxonomies and pointed the fields at them. Might be worth checking if those aren't also defined in controlled_access_terms

[seth-shaw-unlv]

I just spun up the islandora-playbook using the ubuntu/focal64 base box and the genre vocabulary is present... so something is happening with the installer if the genre vocabulary is missing in your build.

[kspurgin]

My build was the sandbox Danny spun up for MIG. 🤷🏻

[seth-shaw-unlv]

@dannylamb, what did you use to spin up the MIG box? The islandora/8 base box or isle_dc?

@mdlincoln, did you use the islandora-playbook or isle_dc for your site? If isle_dc, which make option did you use?

[hachacha]

@seth-shaw-unlv I work with @mdlincoln
We are using isle-dc. We used the make local option after creating the codebase from the make-local-from-demo branch.
I had tried using the islandora-sandbox as the codebase and then using make local but ran in to some issues with the install -- I can speak to that more in a different issue if appropriate

[seth-shaw-unlv]

I'm not very familiar with isle_dc and I'm in a training most of today and the next two days, so I'm probably not the best person to move forward with this. I put out a call on the isle channel of the Islandora Slack, so hopefully someone will be able to give it a look.