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 64
    • Issues 64
    • 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
  • #6034
Closed
Open
Issue created Mar 04, 2020 by Côme Chilliet@cchillietReporter

Handle special values for regimeinsc and sectdisc in supannEtuInscription

There is this weirdness in SupAnn specification:

pour les champs regimeinsc et sectdisc, s'il n'existe pas de valeur appropriée le champ doit contenir ”{INCONNU}”, et l'attribut élémentaire correspondant ne doit pas être renseigné;

So we need to add support for this. On the other hand, I guess we should remove special values NON RENSEIGNE and SANS OBJET pulled from BCN.

Assignee
Assign to
Time tracking