Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-plugins fusiondirectory-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 59
    • Issues 59
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #6047
Closed
Open
Created Apr 29, 2020 by bmortier@bmortierMaintainer

A better way of managing SupAnn lists

Descriptive title for this enhancement

designing a better way to manage supann list

Actual behavior

Actually we read list from disk and those list a created from the bcn

  • activite_CNU
  • activite_REFERENS
  • affiliation
  • corps_NCORPS
  • diplome_SISE
  • discipline_SISE
  • entite_SUPANN
  • etablissement_SUPANN
  • eturegimeinscription_SISE
  • role_SUPANN
  • typediplome_SISE

most of the time the people are not happy with the list because :

  • They are huge an not very usefull for their specific cases
  • they cannot remove entries in the file because it will be erased on next upgrade
  • If the file where not erased but backuped, it still will need manual editing of the file who his cumbersome

Expected behavior

Have to possibility to store lists in the fusiondirectory backend tab supann to replace the lists sroted on disk

Step by step description of new behaviour

  1. Look into his backend to know if a list is filled in the configuration backend
  2. If this list is filled it would just use the data from the configuration backend on would not charge the file form disk

we could to that at startup maybe with a flag telling the plugin which list should be taken from disk and wich not

or

we could just flag the list in the configuration backend as used or not used and stored that in seesion so the plugin now where to look for data

Benefits

  • Better usability for users
  • Better configurability because those list have lots of variations in each location

Possible Drawbacks

need to think ou to split the supann tab in configuration to not getting huge

Applicable Issues

full discussion in french https://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/-/wikis/meeting-supann-list-2020-04-30

Edited May 18, 2022 by bmortier
Assignee
Assign to
Time tracking