-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating a new Islandora Content Type, and UI woes with the media_of field #1239
Comments
We could also add a little form that provides a drop-down list of the content types and a button, labeled something like "Islandora-ize," that slots the new content type into all the configs Rosie mentioned. |
...and that's the friggin' link between islandora_core_feature and islandora_defaults that's been thwarting me forever. Ima gonna verify that once my latest box spins up. |
Nope. Dangit. By default, that field is set up to reference any node type. 😭 Good to know it'll work with new content types, but I was really hoping I found the missing link between those two features. Anyhow, sorry to sidetrack this thread. 👍 to the improvement. |
I've got a small change I'll put in as a pull request if folks think it's a good idea. It just filters through the media types (which are already filtered to show only those types with a media_of field) and only shows those media types which are legal for that content type. I've grandfathered in the semi-legal media types which we get by default with no content type selected yet. |
Wait, @dannylamb , whaddya mean it's "set up to reference any node type"? That sounds like it's in direct opposition to what Alan experienced, where a newly created node type was not enabled by default.
Sounds cool, but to ask a question that demonstrates I don't actually get it: in what part of the interface would you put this filter? |
@rosiel - The media tab on any object allows you to add a new media (trying SO hard not to say datastream). Currently you can select any media type that has a field_media_of field. The filter I've got ready for a pull only shows you media types with field_media_of field that allows whatever content type you're currently on the media tab of. |
lol, pretty much. When you very first attach an entity reference field to a node, it doesn't restrict what types you can reference. As long as you never ever save those field settings again, it can live like that indefinitely. Go change a single field setting and try to save, and it'll force you to choose a type. The reason why we don't lock things down to 'Repository Item' by default is because then that introduces linkages between the core feature and the islandora_deafaults, which we're trying to keep as separate as possible (easier said than done). |
Say I wanted to make a new Drupal content type for Islandora content. This was a closed documentation ticket, #85, and there is a "Create a Content Type" section at https://islandora-claw.github.io/CLAW/user-documentation/content_types/. It is good because it walks you through configuring that new content type to get indexed by Fedora and the triplestore.
@ajstanley noticed that even once you do this, you can't add any Media. If you want to be able to add Media to this new content type, you need to go to Structure > Media Types and "Manage fields" on every single media type to tell the "Media of" entity reference field that it's ok to point to this new content type.
That's unexpected and frustrating. It can be documented, but it's a fundamental mismatch between the Drupal paradigm and the Islandora paradigm.
Modest proposal: Could Islandora ship with a "dashboard" that displays to the user such things as Islandora Managers may want to know without digging through dozens of menus, such as:
Ideally, a user could use this dashboard to manage the settings, but that's probably getting ahead of myself. A display, and information pointing to where these settings can be modified, would go a long way.
The text was updated successfully, but these errors were encountered: