Islandora · Natkeeran · Apr 10, 2019 · Mar 6, 2019 · Mar 6, 2019 · Mar 6, 2019
diff --git a/docs/assets/islandora8_fieldindisplay.png b/docs/assets/islandora8_fieldindisplay.png
diff --git a/docs/assets/islandora8_fieldsettings.png b/docs/assets/islandora8_fieldsettings.png
diff --git a/docs/assets/islandora8_managefields.png b/docs/assets/islandora8_managefields.png
diff --git a/docs/assets/islandora8_newfield.png b/docs/assets/islandora8_newfield.png
diff --git a/docs/assets/islandora8_newfieldinform.png b/docs/assets/islandora8_newfieldinform.png
diff --git a/docs/user-documentation/content_types.md b/docs/user-documentation/content_types.md
@@ -0,0 +1,126 @@
+# Create / Update a Content Type
+
+!!! tip The screenshots and pre-existing data in this documentation assume that you are using the [Islandora Demo](https://github.com/Islandora-CLAW/islandora_demo) configuration. 
+
+!!! tip This page will address how to create and modify ingest forms (or rather, content types) via the GUI. For help working with forms via the API, please check out the [Further Reading](#further-reading) section for links to more advanced Drupal documentation.
+
+Since objects in Islandora 8 are stored in Drupal as Nodes, we use the standard Drupal Content Types system to create and edit our ‘ingest forms’ [Content Types in Drupal 8](https://www.drupal.org/docs/8/administering-drupal-8-site/managing-content-0/working-with-content-types-and-fields). Islandora 8 forms are Drupal forms, and if you are already familiar with Drupal Field UI, you’re already well equipped to create and modify your own ingest forms in Islandora 8.
+
+This page will address how to create and modify ingest forms (or rather, content types) via the GUI. For help working with forms via the API, please check out the Further Reading section for links to more advanced Drupal documentation.
+
+## Modify a Content Type
+
+If you have deployed your Islandora 8 with the Islandora Demo configuration, you will already have a Repository Item content type available, with pre-configured fields. In the Admin menu, go to Structure >> Content Types and find the Repository Item content type. Select *Manage Fields*.
+
+![a screenshot of the Add Content Type page](/docs/assets/islandora8_managefields.png)
+
+You will see a list of the fields that are already available in this content type. 
+
+### Add a Field
+
+Let’s add a new field where a user can indicate if the repository item needs to be reviewed:
+
+1. Click “Add Field”
+1. Since this is a “yes/no” decision, we will use “Boolean” and give the field a name. [List of Drupal 8 FieldTypes, FieldWidgets, and FieldFormatters](https://www.drupal.org/docs/8/api/entity-api/fieldtypes-fieldwidgets-and-fieldformatters)
+1. Now we configure how the field is stored in the Drupal database. For this field type we can select how many values will be allowed. Set this value to "1":
+1. Now we configure how the field is described (including its display label and the help text for when it appears on a form) and constraints on its use. In this case, the field will be required for this Content Type, and will be set to “on” by default: 
+
+![a screenshot of the field settings page](/docs/assets/islandora8_fieldsettings.png)
+
+*Save*. Now we have added our new field: 
+
+![a screenshot of a "Needs Review?" field in the Drupal field UI](/docs/assets/islandora8_newfield.png)
+
+And it appears in the ingest form when we try to create a new repository object:
+
+![a screenshot of a "Needs Review?" field appearing at the bottom of a new node form](/docs/assets/islandora8_newfieldinform.png)
+
+!!! tip New fields, with the exception of Typed Relation fields, are not automatically indexed in Fedora and the triple-store. Update the Content Type's RDF Mapping [link that section of the docs] to enable indexing the field. 
+
+!!! tip To add new behavior based on the results of this new field, check out [link to Context docs]
+
+### Change the Form Display
+
+Now let’s move our new field to a different part of the form. In the Admin menu, return to Structure > Content Types and find the Repository Item content type again. Select Manage form display.
+
+1. All of the fields in this content type are available, in a list, with a simple drag-and-place UI. Drag the *Needs Review?* Field to the top of the form. We can also change the way the Boolean options are displayed, with radio buttons as opposed to a single checkbox. Different display options will be available depending on field type. For more information, please check out [List of Drupal 8 FieldTypes, FieldWidgets, and FieldFormatters](https://www.drupal.org/docs/8/api/entity-api/fieldtypes-fieldwidgets-and-fieldformatters)
+1. Save. When creating a new Repository Item, the *Needs Review?* Field appears at the top, as a set of radio buttons.
+
+### Change the Content Display
+
+Finally, let’s change how the results of this field are displayed. As things stand now, our new field shows up at the bottom of repository object pages:
+
+![a screenshot of a "Needs Review?" field in the node display](/docs/assets/islandora8_fieldindisplay.png)
+
+In the Admin menu, return to Structure > Content Types and find the Repository Item content type again. Select Manage display.
+
+1. Find the *Needs Review?* We can change how the field title is display (inline/above/hidden entirely) and replace the options displayed with variations on a binary choice (yes/no, enabled/disabled, checkmark/X) or hide the field completely. 
+1. We can also drag the field into the Disabled section so that neither its label or its contents appear in the display, although the area saved on the node.
+1. Drag the field to "Disabled" and save.
+1. We no longer see the field on the display, but it is available when editing the node.
+
+## Create a Content Type
+
+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.
+
+
+## Update / Create an RDF Mapping
+
+RDF mapping is aligning drupal fields to RDF ontology properties. For example the title field of a content model can be mapped to dcterms:title and/or schema:title. In Islandora 8, triples expressed by these mappings get synced to Fedora and indexed in the Blazegraph triplestore. RDF mappings are defined/stored in Drupal as a YAML file. Currently, Drupal 8 does not have a UI to create/update RDF mappings to ontologies other than Schema.org. This requires repository managers to update the configuration files themselves. 
+
+The Drupal 8 Configuration Synchronization export (e.g. `http://localhost:8000/admin/config/development/configuration/single/export`) and import (e.g. `http://localhost:8000/admin/config/development/configuration/single/import`) can be used to get a copy of the mappings for editing in a text editor before being uploaded again. Alternatively, a repository manager can update the configuration on the server and use Features to import the edits.
+
+RDF mappings, like all Drupal configuration files, are written in [YAML](https://yaml.org/). YAML is out of scope for this documentation, but there are [several tutorials on the web](https://duckduckgo.com/?q=yaml+tutorial). 
+
+An RDF mapping configuration file has two main areas, the mapping's metadata and the mapping itself. Most of the mapping's metadata should be left alone unless you are creating a brand new mapping for a new Content Type or Taxonomy Vocabulary. 
+
+The required mapping metadata fields when creating a brand-new mapping include the `id`, `status`, `targetEntityType`, and `bundle`. (`uuid` and `_core`  will be added by Drupal automatically.) `bundle` should be the machine name for the Content Type or Taxonomy Vocabulary you are creating the mapping for. `targetEntityType` will be `node` if the bundle is a Content Types or `taxonomy_term` if the bundle is a Taxonomy Vocabulary. The `id` configuration is a concatenation of target entity type and bundle. The `id` is also included in the configuration file name: e.g. `rdf.mapping.node.islandora_object.yml` is `rdf.mapping.` plus the id and then `.yml`.
+
+The mapping itself consists of the `types`' and `fieldMappings` configurations.
+
+All the mappings use RDF namespaces instead of fully-qualified URIs. For example, the repository item's type is `pcdm:Object` instead of `http://pcdm.org/models#Object`. Unfortunately, the available namespaces are defined in module hooks (hook_rdf_namespaces) rather than in a configuration file. Repository managers need to create their own module and implement hook_rdf_namespaces to make additional namespaces available. See the islandora_demo hook implementation for an example.
+
+Namespaces currently supported (ordered by the module that supplies them) include:
+ * rdf
+      * content: http://purl.org/rss/1.0/modules/content/
+      * dc: http://purl.org/dc/terms/
+      * foaf: http://xmlns.com/foaf/0.1/
+      * og: http://ogp.me/ns#
+      * rdfs: http://www.w3.org/2000/01/rdf-schema#
+      * schema: http://schema.org/
+      * sioc: http://rdfs.org/sioc/ns#
+      * sioct: http://rdfs.org/sioc/types#
+      * skos: http://www.w3.org/2004/02/skos/core#
+      * xsd: http://www.w3.org/2001/XMLSchema#
+ * islandora
+      * ldp: http://www.w3.org/ns/ldp#
+      * dc11: http://purl.org/dc/elements/1.1/
+      * nfo: http://www.semanticdesktop.org/ontologies/2007/03/22/nfo/v1.1/
+      * ebucore: http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#
+      * fedora: http://fedora.info/definitions/v4/repository#
+      * owl: http://www.w3.org/2002/07/owl#
+      * ore: http://www.openarchives.org/ore/terms/
+      * rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns#
+      * islandora: http://islandora.ca/CLAW/
+      * pcdm: http://pcdm.org/models#
+      * use: http://pcdm.org/use#
+      * iana: http://www.iana.org/assignments/relation/
+ * islandora_demo
+      * relators: http://id.loc.gov/vocabulary/relators/
+ * controlled_access_terms
+      * wgs84_pos: http://www.w3.org/2003/01/geo/wgs84_pos#
+      * org: https://www.w3.org/TR/vocab-org/#org:
+      * xs: http://www.w3.org/2001/XMLSchema#
+
+The `types` corresponds to the `rdf:type` predicate (which corresponds to JSON-LD's `@type`) and can have multiple values. This type value will be applied to every node or taxonomy term using the mapped type or vocabulary.
+
+In some cases a repository may want a node or taxonomy term's `rdf:type` to be configurable. For example, the Corporate Body Vocabulary (provided by the Controlled Access Terms Default Configuration module) has `schema:Organization` set as the default type in the RDF mapping. However, more granular types may apply to one organization and not another, such as `schema:GovernmentOrganization` or `schema:Corporation`. The `alter_jsonld_type` Context reaction allows Content Types and Taxonomy Vocabularies to add a field's values as `rdf:types` to its JSON-LD serialization (the format used to index a node or taxonomy term in Fedora and the triple-store).
+
+`fieldMappings` specifies the fields to be included, their RDF property mappings, and any necessary data converters (the `datatype_callback`). One field can be mapped to more than one RDF property by adding them to the field's properties list. The `datatype_callback` is defined by the 'callable' key and the fully qualified static method used to convert it to the desired data format. For example, fields of the Drupal datetime type need to be converted to ISO 8601 values, so we use the `Drupal\rdf\CommonDataConverter::dateIso8601Value` function to perform the conversion.
+
+## Further Reading:
+
+* [Drupal.org Introduction to Form API](https://www.drupal.org/docs/8/api/form-api/introduction-to-form-api)
+* [Step by step method to create a custom form in Drupal 8](https://www.valuebound.com/resources/blog/step-by-step-method-to-create-a-custom-form-in-drupal-8)
+
+