Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a project owner of a multi-jurisdiction project, I want to be able to add all tasks to one Project #1450

Closed
goose-life opened this issue Apr 13, 2022 · 4 comments · Fixed by #1846

Comments

@goose-life
Copy link
Contributor

Subject-based projects span jurisdictions, but Projects are place-based.

@goose-life goose-life added the proposal needed Needs a proposal or write-up label Aug 21, 2023
@goose-life
Copy link
Contributor Author

let's chat with the Content team and get a plan in place this sprint

@goose-life
Copy link
Contributor Author

goose-life commented Sep 20, 2023

Issues

Projects are:

  • place-based (so we have many 'Covid-19' or 'Refugees' projects in various jurisdictions)
  • work-unaware (so when a sign-off task is automatically created on a work, it doesn't get added to the project)

Suggestions

  • new ProjectsPlus model, one-to-one to TaxonomyTopic, which holds the project description (cf. peachjam EntityProfile model)
    • should also have priority, date
    • priority should change from boolean to high, medium, low
  • tasks should show the highest priority on the task detail page (either by displaying the priority next to each Project that the task falls under, or by working it out on loading the page and adding an icon towards the top)
  • potentially merge https://edit.laws.africa/tasks/available/ and https://edit.laws.africa/tasks/priority/; add priority filter (as well as taxonomy topic filter, and beef up country --> place filter)
  • change ordering of task listing to high priority by age, then medium by age, then low by age
  • these projects can derive which tasks belong to them via the works with the given topic
  • for 'internal only' projects, e.g. 'continuous update' or 'multiple commencements', add a separate root ('Projects') that won't be exposed externally
  • on bulk import, the 'Projects' dropdown will be a list of the internal topics instead of a list of projects; subject-area taxonomies will be managed in the spreadsheet same as currently
  • global projects view that looks similar to the Projects listing
  • add a place filter here
  • don't list topics with no works
  • only list topics to a certain depth (level 1 or 2)
  • ProjectPlus, allow user to link it to a taxonomy manually
  • global task view which can filter by taxonomy (for those that don't have a ProjectPlus) — change current view to show closed tasks or indicate progress
  • in the global task view, add a simplified taxonomy creation form (only visible to people with Taxonomist badge)

Questions

For Dev team:

  • where and how does the user manage the ProjectPlus objects? (detail view: edit, same as at https://edit.laws.africa/places/za/projects/198/)
  • can we add descriptions to both internal and external topics? (I'd say yes, they shouldn't be treated any differently)
  • do we make 'ghost' ProjectPlus objects for ones that haven't been explicitly created with descriptions, or do we list by taxonomy topic (only if there are tasks), and optionally include the descriptions?
    • short answer is no to ghosts
    • ProjectPlus will link to either an internal or an external topic
    • these are what will be listed
    • so we'll have to create ghost ones
    • each TaxonomyTopic automatically has a ProjectPlus object with an optional description (OneToOne)
    • Actually, let's not create ghost ProjectPlus objects for each topic, because we don't need to list things people don't care about
  • do we save the tasks to their respective ProjectPlus objects, or is it always worked out dynamically?
    • short answer: dynamic; we can do something optimise if needed
    • working out progress bars in the project listing view and in project detail views might become expensive if it's dynamic
    • keeping the ProjectPlus objects up to date will need a bit of work — e.g. every time a new task is created, every time a work's taxonomy topics change, etc
  • what is it going to look like?

For Content team:

  • will they still want the Projects listed per place? or can we only have a global view that includes a place filter?
    • no need for this probably; the place-level project view will fall away to start with

Previous feedback from Content team

  • descriptions are critical
  • progress tracker is super useful

@goose-life
Copy link
Contributor Author

Next steps:

  • meet with Content team and describe what we have in mind; get feedback
  • do a formal write-up with new models, views, etc

@actlikewill
Copy link
Contributor

actlikewill commented Sep 26, 2023

Proposal

Modeling changes

Add a new description field to the TaxonomyTopic Model
description : TextField

  • This allows us to assiociate taxonomy topics with a description

Bulk Import

On the bulk import view, add a drop down to taxonomy topics to allow works to be tagged with a taxonomy.

Views

  • Add a taxonomy filter to the Available tasks view to allow editors to sort tasks by a taxonomy.in
  • Include progress bar when we have a grouping of tasks

@actlikewill actlikewill added impact: medium and removed proposal needed Needs a proposal or write-up impact: low labels Sep 26, 2023
@actlikewill actlikewill mentioned this issue Oct 17, 2023
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants