On Mon, Dec 22, 2025 at 05:40:45PM +0000, Emmanuel Dreyfus wrote:
On Mon, Dec 22, 2025 at 04:58:58PM +0000, Howard Chu wrote:
It's still unclear what you're trying to do in this overlay, so I can't guess at what alternatives might exist.
I did not want to annoy everyone with the details, but here we go.
There is a directory layout specification for french higher education institutes called supann [1]. It defines various attributes, incuding "composite attributes" that fold a lot of data. Here is an example for the attribute that describes student enrollment in a master's degree.
supannEtuInscription: [etab={UAI}0751717J][anneeinsc=2019] [regimeinsc={SISE}10][sectdisc={SISE}38][typedip={SISE}XB] [cursusann={SUPANN}M2][diplome={SISE}2500005] [population={SUPANN}AGEI][datefin=20201130220000Z]
Composite attributes are made of [key=val] components. The specification says that for each component, there must be a plain attribute (named "elementary attribute" in the spec) that holds the value. So if we have the supannEtuInscription above, we must also have: supannEtablissement: {UAI}0751717J supannEtuAnneeInscription: 2019 supannEtuRegimeInscription: {SISE}10 supannEtuSecteurDisciplinaire: {SISE}38 supannEtuTypeDiplome: {SISE}XB supannEtuCursusAnnee: {SUPANN}M2 supannEtuDiplome: {SISE}2500005 supannCodePopulation: {SUPANN}AGEI supannEtuDateFin: 20201130220000Z
Hi Emmanuel, this looks suspicious to me, if supannEtuInscription is multi-valued, how do you handle the other attributes with respect to filters (e.g. supannEtuDateFin comparisons are no longer sane), etc.?
Storing those degrees(?) as separate children entries sounds a little saner, depending on the use case.
Regards,