Reindex: Difference between revisions
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
The integration automatically creates and maintains the school's users in Reindex. Reindex is a web-based service that brings together all features of a modern library system in one manageable user interface. | The integration automatically creates and maintains the school's users in Reindex. Reindex is a web-based service that brings together all features of a modern library system in one manageable user interface. | ||
The UMS integration allows Reindex to retrieve data from the UMS web server. | The UMS integration allows Reindex to retrieve data from the UMS web server. | ||
== Prerequisites == | ==Prerequisites== | ||
=== Module requirements === | ===Module requirements=== | ||
[[UMS]] | [[UMS]] | ||
=== What to have ready === | [[UMS Web]] | ||
===What to have ready=== | |||
An opened firewall directly into the UMS. Typically port 80 or 443. | An opened firewall directly into the UMS. Typically port 80 or 443. | ||
Recommend SSl Certificate on UMS Web server. Due | Recommend SSl Certificate on UMS Web server. Due to sensitiv personal information. | ||
== Installation == | ==Installation== | ||
See [[Configurator/Webservice]] | See [[Configurator/Webservice]] | ||
=== Template Setting === | ===Template Setting=== | ||
Create an option for Students and Employees if different mail domains are used | Create an option for Students and Employees if different mail domains are used | ||
[[File:Reindex0.jpg|none|thumb|557x557px]] | [[File:Reindex0.jpg|none|thumb|557x557px]] | ||
== Technical settings == | ==Technical settings== | ||
Create a Reindex setting. Reindex can only retrieve data from the templates that have an option attached. | Create a Reindex setting. Reindex can only retrieve data from the templates that have an option attached. | ||
Customer ID is used by Reindex to define the customer in their database. It can be anything. | Customer ID is used by Reindex to define the customer in their database. It can be anything. | ||
Tag: Is used to | Tag: Is used to separate instances from one another. This is the tag referred to in [https://reindexknowledge.zendesk.com/hc/da/articles/208816706-UMS ReIndex's documentation] | ||
Mail Domain: Is used to send information back to users. | Mail Domain: Is used to send information back to users. | ||
| Line 29: | Line 32: | ||
[[File:Reindex1.jpg|none|thumb|557x557px]] | [[File:Reindex1.jpg|none|thumb|557x557px]] | ||
== FAQ == | ==FAQ== | ||
===What happens after the configurations are done ?=== | |||
When configurations are done in backend and frontend environments, inLogic is responsible for communicate technical details to Reindex. | |||
As soon as Reindex have implemented the technical details, teachers and students will have access to Reindex through UMS. | |||
Example of an e-mail from inLogic to Reindex | |||
[[File:Mail til reindex.png|left|thumb|Eksempel på mail til reindex]] | |||
Latest revision as of 12:48, 17 September 2024
The integration automatically creates and maintains the school's users in Reindex. Reindex is a web-based service that brings together all features of a modern library system in one manageable user interface.
The UMS integration allows Reindex to retrieve data from the UMS web server.
Prerequisites
Module requirements
What to have ready
An opened firewall directly into the UMS. Typically port 80 or 443.
Recommend SSl Certificate on UMS Web server. Due to sensitiv personal information.
Installation
Template Setting
Create an option for Students and Employees if different mail domains are used
Technical settings
Create a Reindex setting. Reindex can only retrieve data from the templates that have an option attached.
Customer ID is used by Reindex to define the customer in their database. It can be anything.
Tag: Is used to separate instances from one another. This is the tag referred to in ReIndex's documentation
Mail Domain: Is used to send information back to users. Mail Alias : If Mail Alias is not used, UMS will by default use username.
FAQ
What happens after the configurations are done ?
When configurations are done in backend and frontend environments, inLogic is responsible for communicate technical details to Reindex. As soon as Reindex have implemented the technical details, teachers and students will have access to Reindex through UMS.
Example of an e-mail from inLogic to Reindex
