excelerate-america / ea-features

2 stars 0 forks source link

TOOL: EA Admin APP (Name TBD) #23

Open tech-ea opened 2 years ago

tech-ea commented 2 years ago

EA Admin APP

OBJECTIVE

A web app for the internal team to view, edit, and delete data in ea-ecosystem databases. The data includes members data, events, ect...

The App should also allow for creating reports based on queries in addition the apps tables should, contain shortened views of backend data formatted to be understood by non engineers

TERMS

  1. Admin Tools: Contains dashboards and tools designed to be used by both engineering and non engineering member of EA
  2. Elevate Tools: Contains dashboards and tools designed to be used by engineering team members, contents of the folder relates specifically to the Elevate Product
  3. Internal Tools: Contains dashboards and tool designed to be used by engineering team members, majority of the contents refer to the management of the ea-ecosystem and excelerate-app firebase projects

REQUIREMENTS

Membership Collection

Reports:

Views:

Actions:

Events Collection

Reports:

Views:

Actions:

Groups Collection

Reports:

Views:

Actions:

Business Account Collection

Reports:

Views:

Actions:

RISKS

REFERENCE FILES

DEPENDENCIES

Other projects that

TASKS

Membership

Events

Business Accounts

LINKS

lyndon-bot commented 2 years ago

Tools:

lyndon-bot commented 2 years ago

@tech-ea @davidcjanssens:

Important Features:

View Members of the collective app View RSVPs to Events

bandhanEA commented 2 years ago

https://excelerateamerica.retool.com/editor/dev-bandhan-eco-system-admin-panel

davidcjanssens commented 2 years ago

Main question: What do you show to an internal user of this admin? I know we say show member count, which is a number but if we show a table of members or make it easy to lookup a member based on email or ID, then what does an internal user see? I don't think tis the whole backend table.

lyndon-bot commented 2 years ago

Main question: What do you show to an internal user of this admin? I know we say show member count, which is a number but if we show a table of members or make it easy to lookup a member based on email or ID, then what does an internal user see? I don't think tis the whole backend table.

Good point, will add this as an additional need!

tech-ea commented 2 years ago

@lyndon-bot I have been working on how to divide this project into meaningful and actionable chunks. I'd like to update the terminology you have proposed for working with ADMIN-related projects.

In addition to Views, Reports, and Actions I think we need to identify the resource and/or resource-service or resource-connection I think we need to make a distinction between views, reports, & actions connected directly to the data source inside the Admin app and the main resource

flowchart LR

        subgraph firebase
                direction LR
                fb0c[client apis]-->fb0db
                fb0db[data store]-->fb0a
                fb0a[admin apis]
            end
      subgraph snowflake
       direction LR
      snf0c[client apis]-->snf0db
      snf0db[data store]-->snf0a
      snf0a[admin apis]
      end
      subgraph other
      direction LR
      otr0c[client apis]-->otr0db
      otr0db[data store]-->otr0a
      otr0a[admin apis]
      end

   subgraph client_users
       direction TB
       cu1-->cu2
    end
    subgraph client_admin
    direction TB
    ca1-->ca2
    end
    cu1<-->fb0c<--->ca1