Content
View differences
Updated by Parimal Satyal 8 months ago
### Acceptance Criteria
* Add a new menu entry in Administration called "Documents"
* This will eventually have three tabs:
* Types (this feature)
* ~~BlockNote (BlockNote settings, out of scope here)~~
* ~~Collaboration (for Hocuspocus server settings, out of scope here)~~
* 'Types' tab will show a list of what was previously Document categories in Administration → Files → Categories
* There is a "+ Type" primary button in the sub-header to add new Move administration for types
* This points to a create form (the same as the edit form but with nothing pre-filled)
* A BorderBoxTable lists all available types (a minor modification to what has already been implemented to Document categories today), with two columns:
* Name
* Documents (this lists the number of documents of this type)
* The default type has a 'Default' label next to it
* Each type has a More (⋯) menu with these options:
* Edit (same action as clicking the name)
* Make default (makes this the default type)
* Move options depending on position (Move to top; move up; move down; move to bottom)
* Delete
* When deleting a type, there are two possibilities:
* The type is currently used: show a Danger Dialog (warning) that lets the user reassign documents currently using the type to a new type From files (categories)
* The type is currently unused: a simler Danger Dialog (warning)
* The edit screen of a type only has two settings, the same as document categories currently:
* Name (text field)
* Active (checkbox)
* In Administration → Files → Categories,
* _\[open\] Use a blankslate to indicate that document categories have moved to Documents → Types, with a link._
first level
<br>
**Permissions and visibility considerations**
* _\[open\] No special considerations/permissions at a type-level?_ _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _\[open\] It might be wise to create new l18n strings for document 'Types' instead of using ones that are already associated with work packages_ _Key terms and phrases in the key languages_
**Out of scope**
* Additional tabs in <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the 'Documents' entry in Administration:
* BlockNote (BlockNote settings)
* Collaboration (for Hocuspocus server settings) changes._
* Add a new menu entry in Administration called "Documents"
* This will eventually have three tabs:
* Types (this feature)
* ~~BlockNote (BlockNote settings, out of scope here)~~
* ~~Collaboration (for Hocuspocus server settings, out of scope here)~~
* 'Types' tab will show a list of what was previously Document categories in Administration → Files → Categories
* There is a "+ Type" primary button in the sub-header to add new
* This points to a create form (the same as the edit form but with nothing pre-filled)
* A BorderBoxTable lists all available types (a minor modification to what has already been implemented to Document categories today), with two columns:
* Name
* Documents (this lists the number of documents of this type)
* The default type has a 'Default' label next to it
* Each type has a More (⋯) menu with these options:
* Edit (same action as clicking the name)
* Make default (makes this the default type)
* Move options depending on position (Move to top; move up; move down; move to bottom)
* Delete
* When deleting a type, there are two possibilities:
* The type is currently used: show a Danger Dialog (warning) that lets the user reassign documents currently using the type to a new type
* The type is currently unused: a simler Danger Dialog (warning)
* The edit screen of a type only has two settings, the same as document categories currently:
* Name (text field)
* Active (checkbox)
* In Administration → Files → Categories,
* _\[open\] Use a blankslate to indicate that document categories have moved to Documents → Types, with a link._
* _\[open\] No special considerations/permissions at a type-level?_
* _When is it not visible?_
**Translation considerations**
* _\[open\] It might be wise to create new l18n strings for document 'Types' instead of using ones that are already associated with work packages_
**Out of scope**
* Additional tabs in
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of
* BlockNote (BlockNote settings)
* Collaboration (for Hocuspocus server settings)