Task #3685
openFile Format and content of "Quarterly report"
0%
Description
The text format of the lists in
https://membership.documentfoundation.org/mc/reports
is a nightmare. A line example:
[2023-08-27: accepted] 682 Dominique Prieur dominique.sextant@orange.fr
I need the names for the minutes and, as you can see, it's complex to split
the content in just one or two steps. We should request to change the lists
to a CSV style.
I had difficulties to identify the new applications approved in this
quarter (to fill in the item 2 of the formal part). If you check the
Applications
in the last period report (Q3, in case), there aren't differences between
a new application approved and a renewal approved. Do you suggest another
way to identify them?
We had to add manually a person, as he doesn't appear in
the Applications in the last period report (Q3), probably because he sent
his new application in 2023-06-30.
Updated by Andrea Esposito about 1 year ago
- Assignee changed from Marco Marinello to Andrea Esposito
- Start date set to 2023-11-08
Uwe Altmann wrote:
The text format of the lists in
https://membership.documentfoundation.org/mc/reportsis a nightmare. A line example:
[2023-08-27: accepted] 682 Dominique Prieur dominique.sextant@orange.frI need the names for the minutes and, as you can see, it's complex to split
the content in just one or two steps. We should request to change the lists
to a CSV style.I had difficulties to identify the new applications approved in this
quarter (to fill in the item 2 of the formal part). If you check the
Applications
in the last period report (Q3, in case), there aren't differences between
a new application approved and a renewal approved. Do you suggest another
way to identify them?We had to add manually a person, as he doesn't appear in
the Applications in the last period report (Q3), probably because he sent
his new application in 2023-06-30.
1. Do you suggest to change the format of all report files to CSV? Right now the list of all members is already a CSV-like file, and its structure is then verified by the integrity check. Shall we only change the non-standard formats to CSV[-like]?
2. Right now there's no clear separation between new applicants and "renewers". We can check whether the person has a non-null first_membership and create a dedicated section for renewals in the applications report. Does it sound right?
3. The current criterion for the applications to be included in the report is based on creation date. Should we also include applications that are older but were decided in the selected quarter?
Updated by Uwe Altmann about 1 year ago
Andrea Esposito wrote in #note-2:
1. Do you suggest to change the format of all report files to CSV? Right now the list of all members is already a CSV-like file, and its structure is then verified by the integrity check. Shall we only change the non-standard formats to CSV[-like]?
Yep. Especially the "Quarterly report" as described.
Attention - we have an exception: The files for the election system in another format - as specified in my mail from 5.10.!
2. Right now there's no clear separation between new applicants and "renewers". We can check whether the person has a non-null first_membership and create a dedicated section for renewals in the applications report. Does it sound right?
Not sure - is the first_membership value not changed by the finalization run when a new person is accepted? And think of a Person who is a member and misses the deadline to re-apply, but applies then the next quarter again. This then is formally a new member - but the date in first_membership will mislead us.
Maybe we need a flag "Application.IsRenewal" which is set when creating an application - that's the moment we know if the Peopple.MembershipExpires is within the current quarter. Testing this against nul also will mislead us - c.f. above special case.
3. The current criterion for the applications to be included in the report is based on creation date. Should we also include applications that are older but were decided in the selected quarter?
No. We should /only/ include persons whose People.MembershipExpires - membership duration is within the current quarter - those are the accepted ones of this quarter.
The date of the decision (the finalization run) is the binding date.