Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with the report period dates for datasets starting in the middle of the year #183

Open
Erika-NRC opened this issue Mar 4, 2020 · 2 comments

Comments

@Erika-NRC
Copy link

Erika-NRC commented Mar 4, 2020

  1. There is an issue with some projects not starting in January of a year.
    The request I had was for UAFM1904 DataSet, starting in August 2019. The box "apply same dates" for every year was checked and considered the following reporting dates:
  • 2019: from 14 Aug 2019 until 1 April 2020
  • 2020: from 14 Aug 2020 until 1 April 2020 (2021?)
    Making it impossible to report 2020 data from January 2020 to July 2020
    (I had to modify it but in EyeSeeTea testing server it will most likely show the info before I changed.)
  1. Multi year projects starting reporting dates change for each year, making it impossible to enter target for 2021 already in 2020.

Many thanks and regards,
Erika

@adrianq
Copy link
Member

adrianq commented Mar 6, 2020

@Erika-NRC

  1. Yes, this is correct. This is the behaviour we discussed originally with @ardhimanshu It can be changed though. At the moment, we add 1 year (365 days) in the following years. What were you expecting? Something like this:
    2019: from 14 Aug 2019 until 1 April 2020
    2020: from 1 Jan 2020 until 1 April 2021
    Another option we foresee is that when you click on 'Apply same dates' text fields for every year are still editable. Therefore, we apply the aforementioned rule (or the current one) but you can still edit it later on.

  2. This is not particularly easy. As you know, the opening periods for output and outcome are defined for the whole dataset (actual and target). This would require a few changes:

  • Change the interface in the wizard and in the contextual action (right-click) so you can introduce the opening periods separated for target and actual
  • Modify the data entry form to use this new information based on the target/actual dropdown
    Do you want us to proceed with these changes? Do you want these changes for 2.26 or 2.31 or both?

@adrianq
Copy link
Member

adrianq commented Mar 26, 2020

@Erika-NRC Just pinging you here in case you missed our response. I guess you are still discussing this internally but just in case...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants