Policy and Data Management Sequence Diagrams pt.1

This blog presents the sequence diagrams that show the interaction between the user and the different sub-components of the Policy and Dataset Management component.

 

Definition of a Dataset Schema

The following sequence diagram shows the step-by-step process when a user defines a new dataset schema. It starts with the user accessing a form through the web interface, followed by indicating various details such as area, schema name, description, owner, source type, and language. Depending on the source type, the user either specifies the image type or defines the schema fields. The subsequent steps involve the submission of requests to the Dataset Management subcomponent, including the creation of the schema object, sending a POST request, storing the schema in the database, creating a corresponding folder in the EGI DataHub, and finally, informing the user about the successful storage of the dataset schema.

Steps explained:

The user accesses the form provided by the web interface to define a new dataset schema. (Line: 1)

The user indicates the area, the dataset schema name, the description, the owner, the source type, and the language. (Lines: 2-6)

If the source type is an image, the user indicates the image type (7a), otherwise, it defines the fields of the schema. (Line: 7)

The requests are submitted and sent to the Dataset Management subcomponent (Line 8):

The web interface creates the schema object. (Line: 8.1)

The web interface sends the POST request to the Dataset Management subcomponent. (Line: 8.2)

The Dataset Management stores the dataset schema in the database. (Line: 8.2.1)

The Dataset Management creates a folder for the dataset schema in the EGI DataHub. (Line: 8.2.1)

The web interface informs that the dataset schema has been stored. (Line: 8.3)

 

List of Datasets

The process of listing available dataset files for a specific dataset schema involves a series of steps that provide users with comprehensive visibility and access to their data. In the following sequence diagram, we delve into the process initiated by a user through the web interface. Starting with accessing the interface and specifying the desired area and dataset, users proceed to submit their requests to the Dataset Management subcomponent. The diagram illustrates how a GET request is sent from the web interface, enabling the Dataset Management subcomponent to obtain the EGI DataHub directory where the files are stored. Subsequently, all dataset files stored in the designated dataset folder at the EGI DataHub are retrieved. Finally, the web interface presents users with an overview of all available dataset files related to the requested dataset schema, ensuring easy navigation and efficient data exploration.

Steps explained:

The user accesses the web interface to delete a given data schema. (Line: 1)

The user indicates the area and the dataset. (Lines: 2-3)

The requests are submitted and sent to the Dataset Management subcomponent (Line: 4):

The web interface sends the GET request to the Dataset Management subcomponent. (Line: 4.1)

The Dataset Management obtains the EGI DataHub directory where the files are stored. (Line: 4.1.1)

The Dataset Management gets all dataset files stored in the dataset folder at EGI DataHub. (Line: 4.1.2)

The web interface depicts all available dataset files from the requested dataset schema. (Line: 4.2)