1

Topic: Leap year problem

Could we PLEASE get a fix for the Export to NBN Gateway to export February dates in leap years correctly! I'm really getting tired of Dario at JNCC rejecting a load of my records and expecting me to correct them

Craig

Craig Slawson
Staffordshire Ecological Record

2

Re: Leap year problem

Wasn't this fixed? http://forums.nbn.org.uk/viewtopic.php?pid=22514#p22514

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

3

Re: Leap year problem

The only thing I can think of is that R6 is actually holding some Feb month end  dates as 28th Feb. when they should be the 29th. As far as I can see nothing in R6 will now generate these wrong dates. Last year I tested everything I could think of, including data entry and import.   The latest  NBN Addin is converting the dates properly.  If something is going wrong then  I am more than happy to investigate further, but I need to know what the circumstances are.

Mike Weideli

4

Re: Leap year problem

I have had a go at a Report which identifies the date problems and a Batch Update which aims to fix them.  I think it is Ok having tested  it against some live data which has some of these  issues, but a full test is going to take more  work as it will be necessary to introduce the errors covering the full leap year rules (ie is not a leap year if divides by 100 unless it will divide by 400).  The report also identifies errors with month starts, year start and year end dates. 


JNCC_Prob_NBNDates.xml needs to be copied into your report folder. It will give you a report in System Supplied/Problem Identification which will identify Events, Samples and Determination which have the problem and all show the dates which will be used when the Batch Update is run. Try this first to see if you agree with the errors reported and the proposed solution   

JBCCNBN1_dataCorrection.xml needs to go into the Batch Update folder. It will run from Batch Updates/System Supplied/problem Correction (JNCCNBN_dates_1). Take a backup before running this. Run the report again and the problems should have been resolved.

Please proceed with caution using this.

Post's attachments

JNCCNBN1_DateCorrection.xml 5.67 kb, 2 downloads since 2016-03-15 

JNCC_Prob_NBN_Dates.xml 4.46 kb, 6 downloads since 2016-03-15 

You don't have the permssions to download the attachments of this post.
Mike Weideli