FS Steward

Recap: What is FS Steward?

FS Steward is a nodal agency/ org who is willing to take up the responsibility of maintaining the FS participant network. FS Steward may or may not actually share data. The core functionalities as steward are the following:

1. Manage participants (add/ delete organisations and root admin)

2. Monitor network (raise alarms or see security threats etc)

3. Enable participant and general users to make connectors and datasets discoverable

4. Resolve issues or pass them on to FS core (Digital Green)

5. Maintain updates for the connectors

What FS Steward doesn’t do right now?

1. override FS participants decision to make dataset or connector discoverable

2. formulate rules for monetisation of dataset

Current status

We have FS Steward html files and some stuff related to user management.

User management in FS steward has three groups from the same organisation:

1. Admin - Registers with Digital Green and gets access to FS steward

2. Member - Admin can add members who can add participants

3. Guest - View only permission

We also have an interface of FS core where I can add FS steward admin.

We have dataset explorer inside FS participant with the assumption that it will interact with the APIs that are at FS Steward.

Enhancements required

Right now, DG is acting as a steward and as a steward we are formulating the requirement.

1. There has to be user login from participant root admin where root admin can create a profile of their organisation and also request for support or raise tickets/ issues.

2. As a steward, we would want to host the dataset explorer so that non FS connector participants can be onboarded if they see value in just publishing their data.

3. In the initial stages, dataset explorer should not restrict anyone from publishing, that is, for dataset to be published a user need not configure and run the connector.

Requirement

1. Participant root admin login:

   1. Profile:

      1. Name, email id

      2. Organisation details

      3. Server where they have configured

   2. Support:

      1. Description: give details

      2. Log file: upload

2. User roles to be redefined:

   1. Admin: same as earlier

   2. Member: same as earlier

      1. guest member: view permissions only

   3. Participant root admin:

      1. Login and create profile and raise issues

      2. Dataset explorer

   4. General users:

      1. View dataset explorer without signup

      2. Make entries after signup/ login

3. Flow for publishing dataset only:

   1. Any user visiting the FS steward url will have the dataset explorer visible.

   2. Call to action on the main page is “+ New Dataset” which will take the user in the following steps:

      1. If new user:

         1. Step 1: dataset details

            1. Details of dataset (name, option of file or API)

         2. Step 2: contextual details

            1. Name, email id, Org name…

         3. Step 3: files

            1. Sample dataset

         4. Dashboard: (a)

            1. Your entry has been recorded pending verification

         5. From the verification link in the mail: signup

            1. Step 1: password

      2. If an existing user:

         1. Step1: login

            1. username

            2. password

         2. Step 2:

            1. The will see the navigation tabs as per their role

               1. Admin: participant, network, dataset explorer, settings

               2. Member: participant, network, dataset explorer, settings (can’t add users only self and org profile)

               3. Participant root admin: dataset explorer, settings (can’t add users only self and org profiles)

               4. Genera user: dataset explorer, settings (can’t add users)

   3. Call to action: “Pair connector”

      1. If