Members list #345

Open
opened 2026-02-16 18:29:30 +01:00 by karolds · 3 comments
Owner

We can benefit from having a members list containing aktive members. It should have the following features:

  • Get personalia info (name, username/email, etc) From ntnus registry.
  • Have info if they are a member or life time member
  • Have info on when the members fee was last paid.
  • Send a notification if it is more than one year since the members fee have been paid, (propably nice if it checks all members once a year/semester and not continually.)
  • Student status (Student, student outside ntnu or not a student)
We can benefit from having a members list containing aktive members. It should have the following features: - Get personalia info (name, username/email, etc) From ntnus registry. - Have info if they are a member or life time member - Have info on when the members fee was last paid. - Send a notification if it is more than one year since the members fee have been paid, (propably nice if it checks all members once a year/semester and not continually.) - Student status (Student, student outside ntnu or not a student)
karolds added this to the Authentication Next Gen milestone 2026-02-16 18:29:30 +01:00
karolds added this to the Kanban project 2026-02-16 18:29:30 +01:00
karolds moved this to High priority in Kanban on 2026-02-16 18:30:09 +01:00
Owner

There have been

take a look at the past attempts to see if they can be reused/revived, or if anything can be learned from them.

I have not found any of the versions used before mdboh (it is apparently a successor to mdbng, which implies a yet older mdb), but mdboh (both the cli tool and the database) was stored on knakelibrak, and probably exists in principal:/backupz/knakelibrak somewhere.

From my POV, the most important and most difficult part is getting a reliable and up-to-date stream of payments, that probably requires someone (kasserer, probably) to register all paid membership fees in a structured and predictable way in their bookkeeping software in a format that can be imported into the database (username, years paid, payment date, and possibly paid amount (e.g. for old people auto-paying 42NOK/y)). Once this is done, the remaining parts are mostly a user interface and some archaeology into data that is older than the current books, before the endless task of getting people to use the system.


Other comments:

"Get personalia info from ntnus registry" is probably not very useful or predictable, and all of this information already exists in PVVs own passwd file.

What should we do when people do not pay their membership fees? Actually start closing accounts, or just appreciate our paying members and enjoy our new statistics?

There have been - [some](https://wiki.pvv.ntnu.no/wiki/Medlemsdatabase) - [previous](https://git.pvv.ntnu.no/Drift/issues/issues/27) - [attempts](https://git.pvv.ntnu.no/Projects/pvvmdb/src/branch/main) take a look at the past attempts to see if they can be reused/revived, or if anything can be learned from them. I have not found any of the versions used before mdboh (it is apparently a successor to mdbng, which implies a yet older mdb), but mdboh (both the cli tool and the database) was stored on knakelibrak, and probably exists in principal:/backupz/knakelibrak somewhere. From my POV, the most important _and_ most difficult part is getting a reliable and up-to-date stream of payments, that probably requires someone (kasserer, probably) to register all paid membership fees in a structured and predictable way in their bookkeeping software in a format that can be imported into the database (username, years paid, payment date, and possibly paid amount (e.g. for old people auto-paying 42NOK/y)). Once this is done, the remaining parts are mostly a user interface and some archaeology into data that is older than the current books, before the endless task of getting people to use the system. --- Other comments: "Get personalia info from ntnus registry" is probably not very useful or predictable, and all of this information already exists in PVVs own passwd file. What should we do when people do not pay their membership fees? _Actually_ start closing accounts, or just appreciate our paying members and enjoy our new statistics?
felixalb removed the servicessaltsecurity labels 2026-02-16 23:13:53 +01:00
oysteikt added the big label 2026-02-20 12:41:28 +01:00
felixalb removed this from the Authentication Next Gen milestone 2026-02-20 12:47:07 +01:00
felixalb removed the exploration label 2026-02-20 12:47:34 +01:00
Owner

I have asked the new treasurer, aka @frero if he can make sure to store the necessary information to make this at least possible from now onwards.

I have asked the new treasurer, aka @frero if he can make sure to store the necessary information to make this at least possible from now onwards.
Owner

the information has been saved for the past few years fwiw

the information has been saved for the past few years fwiw
Sign in to join this conversation.
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drift/issues#345