1 (edited by burkmarr 25-11-2010 16:30:49)

Re: The weirdest R6 bug I ever saw

I configured term lists to created a new measurement type called 'Atlas Status'. The measurement qualifier is 'Bird' and the measurement unit is of type text and confined to the following allowed values: 'Breeding possible', 'Breeding probable', 'Breeding proven', 'Migrant' or 'Summering'.

I use the import wizard to import a spreadsheet of values including a column for 'Atlas Status' each of whose cells has one of the five allowed values. On import this column is matched to 'Taxon Occurrence Data->Atlas Status of Bird'.

When 'Validate Columns' is clicked, the wizard reports errors for all the records with 'Migrant' or 'Summering' as their value and turns the corresponding cells red.

Okay, you may think that there is obviously some error - either the term lists have been set up incorrectly or there is a spelling error in the cells in the spreadsheet. However, all I have to do is move the mouse pointer over each of the red cells - without pressing any keys or mouse buttons - and the red cells magically turn white! When they are all done, the wizard reports that there are no validation errors!

Sadly the the wizard does not enable its next page button so I cannot procede with the import. I found a workaround which was to deliberately alter one of the values to an incorrect value before clicking the 'Validate Columns' button. Then after I click the button and wave the magic wand mouse cursor to remove the spurious 'incorrect' values, I can fix the one I deliberately altered and the next page button is enabled.

A strange feature of this phenomenon is that it happens on a partner's R6 installation, but on ours - which is set up in the same way - it works without problems.

The workaround is not a very convenient way for our partner to proceed, so if anyone can throw any light on this at all, I would be very grateful.

Rich

Richard Burkmar
Biodiversity Project Officer
Field Studies Council

2

Re: The weirdest R6 bug I ever saw

Hi Richard

Let me guess, after all the cells have turned white you still can't actually continue to do the import?

You might find this post of mine relevant

http://forums.nbn.org.uk/viewtopic.php?id=1454

Rob

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

3

Re: The weirdest R6 bug I ever saw

Thanks Rob! I did do a search - I don't know how I missed it. Yes it is exactly the same problem. I think that my case adds a little more evidence because it works on one R6 setup and not on another. Perhaps our partner's setup already includes term list entries with 'Migrant' or 'Summering' resulting in multiple matches as you have suggested. There is no easy way for me to check this just now - he's on the other side of Liverpool - but I will in due course.

Does the workaround I found for enabling the 'next' button hold out any promise for you?

Rich

Richard Burkmar
Biodiversity Project Officer
Field Studies Council

4

Re: The weirdest R6 bug I ever saw

Ah the workaround, I didn't notice that bit on your post yesterday, maybe I was in a hurry.

I have no idea whether it works or not but I will be sure to try when I have a chance. It certainly casts an interesting light on the problem. It would seem that the next button is activated by a positive response from some kind of validation check which is not happening with these term list problems, probably because there is no actual invalid data to correct.

That ought to narrow it down somewhat.

Rob Large
Wildlife Sites Officer
Wiltshire & Swindon Biological Records Centre

5

Re: The weirdest R6 bug I ever saw

Hi Rob,

No you didn't miss it - we cross posted. I accidentally submitted half of my post before it was finished and was busy editing it when you posted your response! (You're too quick!) Thanks for you help. It does seem like it should be a relatively simple problem for the developers to tackle - I hope they take it on board.

Rich

Richard Burkmar
Biodiversity Project Officer
Field Studies Council

6

Re: The weirdest R6 bug I ever saw

This bug has been logged in the register of bugs/enhancements. It will also be added  to the list of known issues,  together with the workaround.

Mike Weideli

7

Re: The weirdest R6 bug I ever saw

Mike

Are the known issues listed anywhere ?  Also what does the fact that something has been recognised as a bug or enhancment means in terms of getting it fixed or implemented ?

8 (edited by MikeWeideli 02-12-2010 11:59:11)

Re: The weirdest R6 bug I ever saw

A list of the current Error Messages and Known issues can be found in the Recorder Web Site under Resources/documentation/Known issues and errors. http://www.jncc.gov.uk/page-4914

When a bug is found this is investiagted and details logged in a tracking system (Mantis). Request for changes are also logged in this system.  This makes sure that nothing is forgotten, but  does not guarantee that the bug will be fixed or the enhancement made. Periodically, normally following a release, JNCC review the list and determine priorities for the next release. Bugs in the core system will receive the highest  priority especially if there is no workaround. Beyond this priority is likely to be given to the fixes and enhancements which benefit the most users. What actual gets done then depends on the funds available. Currenty the higest priority is being given to fixing the dictionary issues. The NHM who are responsible for maintaing the dictionary have proposed a new structure, which should overcome the problems in sorting and reporting down the taxonomic hierarchy which are currently of major concern. Recorder will need to be modified to use this new structure and this is being given the highest priority.

Mike Weideli