Nomenclature of features in Pixlie

[brainless]

We want to discuss the nomenclature of features in Pixlie so that we have something to adhere to inside our codebase as well as in our product/marketing efforts. Here are some of the broad ideas we should discuss (not an exhaustive list):

1. Data sources: web (crawling), hosted drives, local computer, etc.
2. Graph - named entities, relations between entities - what is at the core of Pixlie AI
3. Large/small language models Pixlie AI uses
4. Machine learning tools Pixlie AI uses
5. Prompt - what do you want to ask AI
6. Entity extraction rules (these are also prompts, but mostly auto generated)
7. Model selection logic
8. Project - prompt, graph, llm/ml tools, model preferences, entity extraction rules all into a "folder"
9. Sharing - how a user can share a "project", privacy rules
10. Team/organization - a group of users who are governed by admin specified sharing/privacy rules

[miteshashar]

Workspaces – a user can be a part of more than one workspaces isolated from each other.

[brainless]

@miteshashar How would you define a Workspace and how is it different from a Project?

To me, a Project sounds like a goal based container, like some analysis I want to get through Pixlie.

Workspace sounds like the settings for data sources, models that can be used, other technical resources. Basically the settings regarding data source, processing and privacy. Multiple projects should be able to use the same workspace.

To me, user sharing settings come under Team and management of multiple teams come under Organization.

[miteshashar]

Yes. I agree with your definition of a Workspace. A Workspace as I see it, contains multiple projects.

Project sounds like a goal based container, like some analysis I want to get through Pixlie.

I agree on this taxonomically. However as a user, I would see a project in a more macro-functional way most of the times. A project is a collection of multiple things related to a project, not necessarily limited to analyses. For e.g. within a project, I could define specific domains or URLs as project-specific data sources.

In the longer run, we should aim for granularity and separation of concerns. For e.g. an Organization(and an Individual likewise) could even have multiple Workspaces?(we should discuss the nuances of this) That way they can share Workspaces more granularly too. I can see value in it at least for Organizations having a large number of people.

Another thing I realize is Organization & Team could mean different things too. Take Github Org containing multiple Teams as an example reference.

Also, for our MVP and initial milestones, we could defer the idea of Workspace and run everything under a single 'Workspace', making it transparent for the beginning? Or just introduce it later.
This depends on whether it serves a crucial purpose initially.

[brainless]

Project and rules

Continuing from your ideas @miteshashar, what if we build this already as a granular mechanism where user/admin can mix and match? For example:

1. Data source, AI/ML model preferences, Running cost limits, Storage location, Domain rules, Topics, etc. can be simple rules
2. User can mix rules into a Project
3. The Goal(s) is manually set for each project
4. Goal(s) generate some of the prompts and related data processing rules
5. User can re-use non-goal related rules from another project (clone a project to start a new one)

We do not need a Workspace in this manner, less confusion. Team/Organization still controls authentication, authorization and permissions.

Individual, organization and team

1. Each user starts as an Individual
2. When user simply wants to share a project, they create a Team and add members to it
3. Teams created by individuals stay on their computer and have simple authentication, authorization and permissions rules
4. Organization can be created when that (paid) feature exists
5. Organization can have teams
6. Organization can have granular authentication, authorization and permissions rules
7. Organization level rules (same rules as mentioned above and more) control teams and projects that belong to it

[HilaryTorn]

So would it be Organization -> Team/Workspace -> Project

aka: Pixlie -> Marketing -> Lead Gen Project

[miteshashar]

Rather, Organization/Team^**/Individual --own--> Workspaces --contain--> Projects.

So, Pixlie --owns--> Marketing --contains--> Lead Gen Project.

^** Not sure I would put it here yet. Ref: #43 (reply in thread)