In Anjana all users have access to the technical or functional metadata of the objects included in the Data Portal because they are centralised in the common repository. However, although the metadata is public, the data is not available to all users and it is these users who must proactively request access to it.
To do so, in Anjana the user has a shopping cart to which they can add approved DSAs or data structures (datasets, reports, metrics… any non-native entity belonging to the organisation).
During the “purchase” process and always through DSAs, the user is presented with different contract options whose terms they must accept in order to proceed.
Once the process is complete, the user will have the necessary permissions in the technology corresponding to the data structures in order to access the data and start consuming it.
To do so, by clicking the cart icon, the user can access the panel with their shopping cart where all the objects for which they wish to request adherence are displayed.
Cart objects for which there is no approved DSA in Anjana, and therefore for which it is not possible to request adherence, are marked with the specific information (“DSA not available”).
On the other hand, cart objects may have been deprecated or expired due to changes and, therefore, may not correspond to the most up-to-date version of the object. For this reason, a message is shown to the user indicating that there is a more recent approved version (“Approved version available”).
From this panel, the user has two buttons available:
-
Request new DSA: With this option the user can submit a request to create a new DSA that allows, through adherence, access to the data in the structures the DSA contains.
This option can be used to include in the request objects not contained in any approved DSA in Anjana, or to request the creation of a DSA, even when another one already exists, that allows the use of data under less restrictive licence terms than the existing one or with a longer expiration date, for example.
In any case, when requesting creation, the user must write the reason for the request and the notification will reach whoever has been defined in the Anjana configuration. This reason can be entered in the various languages configured in the application.
-
Go to adherences: With this option the user starts the adherence request process by entering a new screen:
This screen shows the user's cart and includes the Request new DSA button available on this screen, which is the same as described above.
As the user advances in the adherence process, Anjana shows the optimal combination of DSAs that give the user access to the included objects for which there is an approved DSA in Anjana.
The optimal combination will be the one that includes the fewest number of DSAs and, if equal, the one that gives access to the fewest possible structures (outside the list requested by the user). But it is possible that this combination may not be valid for the user, which is why they have the option to Load more combinations.
By clicking on this option, Anjana calculates a configurable number of possible combinations that give access to the list of objects in the user's cart.
With this information, the user can assess which combination is most suitable (both in terms of the contracts they include and the expiration dates and other metadata included in the DSAs) and, once one is chosen, Anjana shows the information associated with each DSA so that the user can accept the licence terms of all of them, enter the reason for requesting adherence, and submit the request.
The DSA expiration date informs the user until when, if their adherence request to the DSA is approved, they will have access to the data within it.
At this point a validation workflow is triggered and the objects for which adherence has been requested disappear from the cart.
When the workflow completes successfully, the user becomes adherent to the DSA and, therefore, has access to its structures' data. If there is active governance over them, this access materialises by granting the user the appropriate permissions in the platform directory.
Direct adherence
If the user decides to request adherence to a DSA, they can do so directly from the Portal or from the DSA view itself using the Adhere action.
In this case, it is not necessary to use the wizard shown previously for the cart; instead, the DSA contract is directly shown to the user for download, together with a text box for entering the reason for the request.
When the user completes the request, the validation workflow is triggered in the same way as described for the cart-based request.