Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and 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
  • fusiondirectoryfusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #6024
Closed
Open
Issue created Jan 21, 2020 by Côme Chilliet@cchillietReporter

SupAnn 2018 second revision new schema, lists and fields

SupAnn 2018 had a second revision: https://services.renater.fr/documentation/supann/supann2018/recommandations2018/fonctionnel/revisions2018

  • supannAdressePostalePrivee, supannTelephonePrive, supannMailPrive added to SupAnn tab. Sounds like supannMailPrive is redundant with supannnMailPerso but it is not said that supannMailPerso is deprecated.

  • homePostalAddress, homePhone seem to be used to indicate which value of supannAdressePostalePrivee and supannTelephonePrive is the main one as I see it, so we may implement them like this.

  • The schema changes from last revision are only added attributes so update is safe.

  • We also need to update nomenclatures to make sure they reflect the last data.

Edited Jul 29, 2021 by bmortier
Assignee
Assign to
Time tracking