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.

changed milestone to %FusionDirectory 1.4

added plugin-supann label

added 3d 7h of time spent at 2020-01-21

subtracted 3d of time spent at 2020-01-21

subtracted 5h of time spent at 2020-01-21

mentioned in issue #6025 (closed)

Split the supannConsentement question in a separate ticket in #6025 (closed)

mentioned in commit a0c60082

mentioned in commit 4989b782

For « {SILLAND} : code sur 4 lettres issu de la table FONCTION_SILLAND d'Harpege.», I cannot find a public source, is this nomenclature publicly available?

added 3h of time spent at 2020-01-22

mentioned in commit c99e3fb1

mentioned in commit e537bc92

mentioned in commit 1a9ff0c3

mentioned in commit 8eb2ff77

homePostalAddress and homePhone are already in the main user tab, so we cannot change their behavior.

I added support for supannAdressePostalePrivee, supannTelephonePrive and supannMailPrive. Documentation for supannMailPerso states «Remarques: si l'attribut supannMailPrive est également renseigné, les valeurs du supannMailPerso DEVRAIENT aussi y figurer. » So, maybe we should remove supannMailPerso or hide it and automagically migrate it to supannMailPrive with {PERSO} tag, not sure.

All nomenclatures from BCN have been updated.

role_SUPANN was not updated, it’s not a 100% clear what should be in it.

https://services.renater.fr/documentation/supann/nomenclatures-proposees

added 3h of time spent at 2020-01-23

mentioned in issue #5906 (closed)

changed title from SupAnn 2018 second revision to SupAnn 2018 second revision new schema, lists and fields

changed the description

added PJ1802-0188 label

changed due date to January 28, 2020

There is a PHP error related to activite_RIME invalid format

Should be fixed

mentioned in commit 36b984a1

added 30m of time spent at 2020-01-29

removed due date

added To Be Tested label

added user-manual label

mentioned in issue user-manual#109 (closed)

I tried to add few attributes related to RIME and I didn't saw any PHP errors

added 32m of time spent at 2020-05-04

removed To Be Tested label

added To Be Tested label

added release notes label

marked this issue as related to #5906 (closed)

removed To Be Tested label

added Added label

closed

changed the description