Skip to content
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.

Sign up for GitHub

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

Update content_types.md #2238

Merged
merged 2 commits into from
Jun 15, 2023
Merged

Update content_types.md #2238

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
43cb639
Update content_types.md
joshdentremont Jun 2, 2023
f5a4992
Update content_types.md
joshdentremont Jun 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 3 additions & 7 deletions docs/user-documentation/content_types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,15 +93,11 @@ In the Admin menu, return to **Structure** >> **Content Types** and find the _Re

To create your own custom content type from scratch, please refer to [this guide](https://www.drupal.org/docs/8/administering-drupal-8-site/managing-content-0/create-a-custom-content-type) on Drupal.org.

Custom content types are not synced to Fedora or indexed by the triple-store by default. Repository managers must add them to a context that instructs Drupal to perform these synchronizations. In the Islandora Starter Site, the "Content" ('repository_content') context does this. To add a new content type to that context:
Your custom content types can contain whatever fields you like, but there are two mandatory fields that all Islandora content types should contain:

1. Navigate to the _Contexts_ configuration page ('/admin/structure/context').
1. Find the _Content_ context and click the corresponding **Edit** button ('/admin/structure/context/repository_content').
1. Find the _Node Bundle_ condition in the _Conditions_ section.
1. Click the checkbox for the new Content Type.
1. Scroll down to the bottom of the page and click **Save and continue**.
1. In order for a custom content type to be considered an Islandora Object, it needs to have the field "Member of" ('field_member_of'). This allows it to be included in contexts that have the "Node is an Islandora node" condition. Nodes that have this field will automatically be synced to Fedora and indexed by the triple store if you are using the context provided by the Islandora Starter Site. Having this field present in your content type also gives you tabs for adding children and media when viewing an item of that content type.

Updating contexts does not retroactively fire any actions. Any of the custom content type's nodes that were created before updating the context will need to have the indexing action manually triggered.
2. The other mandatory field is "Model" ('field_model'). This is used in several of the contexts that the Islandora Starter Site provides. This field determines how Islandora objects are diplayed, and how media derivatives are created.

## Updating and creating an RDF Mapping

Expand Down