Skip to content

specify the rules for the perimeter of order visualizations

Some users should be able to visualize orders (but not actually modify or create them).

Visualizing orders can consist in

  • simply listing orders and being able to view their details (is it necessary?)
  • download them (in CSV format for example)
  • see statistics about them

We decided that the permission should be associated with a "level", which can be "global", or a speficic GRC, or a specific accession holder.

Now, when it comes to the visualization itself, should the user always see the same perimeter, or should he/she be able to select a more precise perimeter. For example:

  • if Joe can see orders at the global level, will he always download and see statistics about all the orders, or should he be able to select a specific GRC or a specific accession holder to only view/download/see statistics about orders of this specific GRC or accession holder?
  • if Alice can see orders for the GRC "GRC1", will she always download and see statistics about all the orders of GRC1, or should she be able to select a specific accession holder of GRC1 to only view/download/see statistics about orders of this specific accession holder?
  • should this perimeter selection, if necessary, allow the selection of multiple GRCs/accession holders, or only one?

Regarding the downloads and statistics, on which time frames should they be computed. Example possible time frames:

  • the current month
  • the last month
  • the current year
  • the last year
  • the complete history
  • a custom date range
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information