...
Shared information is viewable by all members of the consortium. Only the users associated with a particular library can edit this information.
Local information includes specific data elements and notes that a library might wish to store about another library in the consortium. This information is viewable and editable only by the library that has created it.
Directory metadata
...
Directory entry information
Data element | Description |
---|
Name | The name of the organizational unit described by the directory entry. |
Type | The type of organizational unit described by a directory entry Options include:
|
Slug | A unique identifier for the directory entry. The slug must be chosen when the directory entry is established, and it cannot be changed once created. Slugs must be unique. |
LMS location code | A location code that corresponds to the code used by the local library management system. For pickup locations, the LMS location code will be used in the NCIP AcceptItem query to place a hold for the requesting patron. |
Symbols | Symbols allow a unit to indicate its unique identifier in one of the following namespaces:
Symbols are only required for root directory entries, which must have at least one symbol. ReShare uses the ISIL namespace by default to encourage standards compliance. Institutions that do not have an ISIL symbol can use one of the other options. |
Units | Each directory entry may have units that represent divisions of the parent entry. The hierarchy for a particular directory entry may have any number of levels and be configured according to each institution’s organizational structure. Each institution is required to have at least one unit. It is recommended that additional units be created for the following reasons:
|
Tags | Tags are keywords or terms assigned to a directory entry. Users can create tags as needed in a fairly informal way. Directory tags can be deleted using the Settings app, as long as they are not in use on any records. The “pickup” tag is a special tag that allows a unit to function as a pickup location. If a directory entry has the “Pickup” tag, it will be displayed as a pickup location in the request confirmation screen when a user submits a request to ReShare. |
Contact information
Data element | Description |
---|---|
Main phone number | The primary phone number for the unit. The main phone number from the requester’s root entry will appear on the pull slip. |
Main email address | The primary email address for the unit. The main email address from the requester’s root entry will appear on the pull slip. |
Main contact name | The name of the primary contact person for the unit. |
Service accounts
Service accounts define the endpoints that are used to facilitate communication and integrations across the ReShare environment. Service accounts first must be defined in the Settings app before they can be assigned to a Directory entry. Please see the Directory Settings documentation for more detail about the types of service accounts that can be created.
Service accounts include:
Slug: A unique ID assigned that identifies the combination of a particular service and directory entry.
Service: The service, chosen from the list of services configured in the settings app.
Account details: A freetext note for any account details relevant to the service.
Custom properties
Data element | Description |
---|---|
Accept returns | Allows a library to set and publish a status indicating whether it is available to accept returns of loaned material at the current time. |
ILL loan policy | Allows a library to set and publish a status indicating the types of lending it is currently supporting. Options include:
|
ILL loan to borrow ratio | Allows a library to determine the loan to borrow ratio it wishes to achieve. This ratio will be used by ReShare’s load balancing algorithm to choose the optimal supplier. ReShare cannot guarantee that a library will adhere exactly to its desired ratio, but will attempt to match it as closely as possible based on availability across the consortium. |
Local directory
...
information
Data element | Description |
---|---|
Institutional patron ID | This field stores a patron ID or barcode that will be used to checkout an item being supplied to the library associated with the directory entry. Local directory fields are visible to your library only and are not shared across the consortium. |
...