{% blocktrans %}

Functions are discrete operations that can be associated with a Resource Model and are run on specific nodes or nodegroups whenever a user clicks creates or modify's a Resource. Here in the Function Manager you will associate Functions with this Resource Model and configure them appropriately.

To add a Function to this Resource Model, click on it in Function Library, and notice that it is added to the list of Selected Functions. To delete a Function, use the symbol in the upper right corner. {% endblocktrans %}

{% blocktrans %}

Arches comes with three default functions (see below). However, functions are envisioned as the hook through which developers can easily customize Arches capabilities, because new Functions can be added to your individual Arches installation. Learn more here.

{% endblocktrans %}

{% blocktrans %}

This function will generate one or more descriptors for Resources that are created with this Resource Model. These descriptors are used throughout the database interface, but are not saved as part of the resource. This gives you control over the way Resources are identified and described in search results and elsewhere.

Once added to the Resource Model, use the appropriate tab to configure a descriptor template. Choose a nodegroup, and variables corresponding to each node in that node group will be added to the template, demarcated with < >. You can rearrange these variables and add text to customize the descriptor.

Note that if there are multiple instances of a given nodegroup in a Resource, the first one added will be used to create these descriptors. To manually change this, edit the Resource in question and drag the desired tile to the top of the list.

{% endblocktrans %} {% blocktrans %}

Note: Any user with read access permission to a resource will be seeing these resource descriptors wherever it shows up in search results or on the map. If a card is intended to be hidden from any group of users, it should not be used in this function.

{% endblocktrans %}

---

{% blocktrans %}

Example

Consider a Resource where the Appellation node value is Folsom School and Appellation Type node value is Primary.

Selecting the Appellation nodegroup will populate the template with <Appellation Type>, <Appellation>. The resulting descriptor would read Primary, Folsom School. Changing the template to Building Name: <Appellation> would yield Building Name: Folsom School.

{% endblocktrans %}

{% trans "This function performs the actual file upload that must occur in order to upload a digital file, like an image, to your database. In Triggering Nodegroups you must select the nodegroup that contains the file-list node. Select multiple nodegroups if there are multiple file-upload nodes this Resource Model's graph." %}