{% blocktrans %}In this tab you will design the graph—the core of a Resource Model or Branch. In fact, sometimes Resource Models and Branches are generically referred to as "graphs".{% endblocktrans %}
{% blocktrans %}For the first step in building a graph, you should fill out the top-level settings. Some of these may be changed later while others can't, so make sure to do a lot of testing while developing a graph. With the top-level settings in place, it's time to construct the graph by adding nodes (or full Branches) to the graph tree. Along the way, you'll need to set the node-level settings for each node you create.{% endblocktrans %}
{% blocktrans %}Once you've finished creating this Resource Model or Branch make sure to set its status to "active".{% endblocktrans %}
| {% trans "Name" %} | {% trans "Used to identify this Resource Model throughout the app interface. Default is New Resource Model." %} |
| {% trans "Subtitle" %} | {% trans "Optional subtitle, displayed on the Arches Designer home page." %} |
| {% trans "Ontology" %} | {% blocktrans %}Decide whether an ontology will be enforced in this graph. To learn more about what this means, read Ontologies in Arches. By default, you are allowed to choose between using the CIDOC CRM v6.2, or using no ontology. Once a node or branch has been added to this graph the Ontology setting cannot be modified.{% endblocktrans %} |
| {% trans "Root Class" %} | {% blocktrans %}This setting is only necessary if an "Ontology" has been chosen. Define the ontology class of the root node for this graph.{% endblocktrans %} |
| {% trans "Status" %} | {% blocktrans %}Set to "inactive" to disallow use of this graph during development. Inactive Resource Models cannot be used to create new resources, and inactive Branches can not be added to a Resource Model.{% endblocktrans %} |
| {% trans "Resource models that may be related" %} | {% blocktrans %}Choose which Resource Models can be related to this one with resource-to-resource relationships.{% endblocktrans %} |
| {% trans "Root Node Data Type" %} | {% blocktrans %}Choose what data type to use for the root node of this Branch.{% endblocktrans %} |
| {% trans "Author" %} | {% blocktrans %}You can optionally add an Author to this graph. Only administrators will see this information.{% endblocktrans %} |
| {% trans "Abstract" %} | {% blocktrans %}You can optionally add an Abstract to this graph.{% endblocktrans %} {% if graph.isresource %}{% blocktrans %}Users will see this abstract when they are presented with a choice of what Resource Model to use to create a new resource.{% endblocktrans %}{% else %}{% blocktrans %}This abstract will be shown in the Branch Library which is used during graph construction.{% endblocktrans %}{% endif %} |
| {% trans "JSON-LD Context" %} | {% blocktrans %}Add a JSON-LD Context for this Resource Model. This allows you to namespace common URI endpoints that are used within a JSON-LD output of the resource. You can enter a plain URL ("http://www.cidoc-crm.org/cidoc-crm/"), or JSON that defines multiple keys ({"crm":"http://www.cidoc-crm.org/cidoc-crm/","rdf":"http://www.w3.org/1999/02/22-rdf-syntax-ns#"}).{% endblocktrans %} |
| {% trans "Color" %} | {% blocktrans %}Choose a color for this Resource Model to be used in the related resources force directed graph.{% endblocktrans %} |
| {% trans "Icon" %} | {% blocktrans %}Choose an icon to identify this graph throughout the app interface. You can browse the icons to select one, or type in the search bar to filter them. Arches uses the Font Awesome icon library; custom icons are not supported.{% endblocktrans %} |
{% blocktrans %}Use the graph tree on the left side of the page to construct the graph. Every new graph starts with a Top Node, which will take the name of the new Resource Model or Branch. From this node, you can either Add Child Node to add a single node, or Add Branch to add an entire existing Branch.{% endblocktrans %}
{% blocktrans %}At any point during construction you can switch from Design mode to Preview to see the full shape of your graph.{% endblocktrans %}
{% blocktrans %}If you have created a branch structure in a Resource Model that you would like to use in a different Resource Model, you can export it from the graph tree.{% endblocktrans %}
| {% trans "Node Name" %} | {% trans "Set the name for this node. This will be used by default in the user interface, but a different name for display can be configured at the widget level." %} |
| {% trans "Ontology Class" %} | {% blocktrans%}only present if this graph uses an ontology{% endblocktrans %} {% blocktrans %}This setting assigns an ontological class to this node. To learn more, read Ontologies in Arches{% endblocktrans %} |
| {% trans "Relationship to..." %} | {% blocktrans %}Define what relationship this node has with its parent node (the one directly above it in the graph tree). A verbalization of your choice is shown in the Semantics section below this setting.{% endblocktrans %} |
{% blocktrans %}Depending on which data type you choose, you may have many more settings to fill out. Those listed below will be present for every node no matter the data type.{% endblocktrans %}
| {% trans "Data type" %} | {% trans "Choose the data type for this node. Please see the Default Data Types section below. Once data is collected for this node, this setting cannot be changed." %} |
| {% trans "Expose to Advanced Search" %} | {% blocktrans%}If true users will be able to add this node to an Advanced Search query.{% endblocktrans %} |
| {% trans "Required" %} | {% blocktrans %}If true a value must be entered for this node in order to save it. Once data is collected for this node, this setting cannot be changed.{% endblocktrans %} |
| {% trans "Place node(s) in a separate card" %} | {% blocktrans%}only present if this node is not already the top node for a card{% endblocktrans %} {% blocktrans %}If true this node will be set in a different card from its parent. This affects data entry, and you are encouraged to test both states of this setting while building you graph. Once data is collected for this node, this setting cannot be changed.{% endblocktrans %} |
{% trans "The data type of a node determines what kind of data that node will store. Once chosen, some data types will require further configuration." %}
{% blocktrans %}Developers can create new datatypes.{% endblocktrans %}
| {% trans "boolean" %} | {% blocktrans %}Use this to store a "yes"/"no" or "true"/"false" value.{% endblocktrans %} |
| {% trans "concept" %} | {% trans "Stores one of a series of concepts from the Reference Data Manager. Users will choose a concept in a dropdown list or set of radio buttons. You'll further be prompted to choose a Concept Collection—this controls which concepts the user is able to choose from." %} |
| {% trans "concept-list" %} | {% trans "Stores multiple concepts in a single node." %} |
| {% trans "date" %} | {% trans "Stores a CE calendar date. See etdf for BCE and fuzzy date handling." %} |
| {% trans "edtf" %} | {% trans "Stores an Extended Date/Time Format value. Use this data type for BCE dates or dates with uncertainty. This datatype requires extra configuration to inform the database search methods how to interpret EDTF values. Data entry users can enter edtf dates using formats listed in the EDTF draft specification." %} |
| {% trans "file-list" %} | {% trans "Stores one or mores files. Use this to upload images, documents, etc." %} |
| {% trans "iiif-drawing" %} | {% trans "Used to store an IIIF compliant image." %} |
| {% trans "geojson-feature-collection" %} | {% trans "Stores geographic coordinates, and is used to show a resource on the map." %} |
| {% trans "domain-value" %} | {% trans 'Similar to "concept", choose this to present the user with a dropdown list or set of radio buttons. Unlike "concept" this dropdown menu will not come from your system-wide controlled vocubulary, but from a list of values that you must define here.' %} |
| {% trans "domain-value-list" %} | {% trans "Stores multiple domain-values in a single node." %} |
| {% trans "csv-chart-json" %} | {% trans "Stores a csv chart formatted as JSON." %} |
| {% trans "node-value" %} | {% trans "Stores a reference to a different node in this graph. This would allow you to store duplicate data in more than one branch." %} |
| {% trans "number" %} | {% trans "Stores a number." %} |
| {% trans "resource-instance" %} | {% trans 'Embeds a separate resource instance into this node. For example, you could add a node called "Assessed By" to a condition assessment branch, and use this data type. This would allow you to associate an individual stored in your database as an Actor resource with a specific condition assessment. Note that this construction is different from making a "resource-to-resource relationship". ' %} |
| {% trans "resource-instance-list" %} | {% trans "Stores a list of resource instances in a single node." %} |
| {% trans "semantic" %} | {% trans "A semantic node does not store data. Semantic nodes are used where necessary to make symbolic connections between other nodes, generally in order to follow ontological rules. The top node of every graph is a semantic node." %} |
| {% trans "string" %} | {% trans "Stores a string of text. This could be something simple like a name, or more something elaborate like a descriptive paragraph with formatting and hyperlinks." %} |