Skip to content

Set up the Projects concept #79

@markwhiting

Description

@markwhiting

Projects have 2 main components:

  • a list of features (a subset of all the features we have, including any features they have added)
  • a list of papers (a subset of all the papers we have which can be manually imported or imported with a criterion search)
  • Perhaps things like a name, a description, and an ID, used to form the URL too.
  • an inclusion criteria stored as a search based of features

They have a secondary component which is that the list of papers may be derived via an inclusion criterion, which is a function written over a set of features (which probably could be different than the features listed in the project). Conceptually, this is like a saved search, which might notify the user when a new item passes the search.

Project ownership and permission can be ignored for now. So everyone can create, delete, and modify any project, including the feature list, etc.

Projects are not published, however every user sees a list of the projects they have viewed (or made) in reverse chronological order perhaps just at /projects.

Should we be able to duplicate, perhaps?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions