System allows keyDate=yes in multiple dates

Project:RUcore Workflow Management System (WMS)
Version:7.6
Component:Metadata
Category:bug report
Priority:normal
Assigned:yuyang
Status:postponed
Description

All originInfo dates have an option to designate the date as keyDate. According to the specs, "keyDate=yes is a directive to sort on this date; allow
only one keyDate per record." (See table under #2.) I input four dates in originInfo (issued, created, copyright, other) and marked all as 'yes' under Sort by this date. Only one should be allowed, since the system needs a single date to sort on in a multiple record display.

Comments

#1

Version:5.2» 5.3
Assigned to:yuyang» mbweber

#2

Assigned to:mbweber» yuyang

This change has been approved by MDWG on 7/18/2011. WMS needs to validate all the dates entered and allow only one date to have keyDate=yes. WMS should present an input error message to the metadata creator and prompt the metadata creator to fix the data entry before saving the record.

NOTE: Currently this field is not used by RUcore search/index for sorting.

#3

Version:5.3» 6.2

Moving from 5.3 to 6.2.

#4

Version:6.2» 7.0

#5

Status:active» test

Test when release 7.0 moves to rep-devel/test site. -YY

#6

Assigned to:yuyang» jjotto

Please test.

#7

The problem is still there. In the Ottobahn Collection, in the record entitled 'Testing title-fullest record,' I input a date issued, date created, and copyright date, all with 'sort by this date'=YES. The system accepted all dates.

WMS must allow only one date to have keyDate=yes. The metadata creator should get an error message if more than one date has 'sort by this date' value of YES.

The message could read: "You can only select one date to sort by."

This problem applies across the entire metadata record. There can only be one 'sort by this date' value of YES in the *entire* record (descriptive, source, technical, rights).

#8

Status:test» active

I think I forgot to change this back to 'active' when I tested last time. The problem is still there, as described above.

#9

Assigned to:jjotto» yuyang

Assigning to Yang.

#10

Status:active» test

Test. -YY

#11

Assigned to:yuyang» jjotto

Jane,

here is another one for you.

KA

#12

Status:test» active

This *almost* works, and thank you, your error messages are much better than the one I proposed.

However I was still able to find a glitch, using the following scenario:

1. Input an originInfo date with 'sort by the date' = yes
2. Either save the record or click 'Save more ...' to save the information in that element
3. Remove the date (as if you've made a mistake)
4. Input new date in the same element (as if you've changed your mind or found new information), with 'sort by the date' = yes
5. Error message appears 'Sort-by (keyDate) has already been set for this element.'

#13

Version:7.0» 7-x
Assigned to:jjotto» yuyang

Moving this to 7-x.

#14

Version:7-x» 7.4

#15

Version:7.4» 7.5

#16

Version:7.5» 7.6

Moving to R7.6. This is not critical.

#17

Status:active» postponed

Jane, I am sorry, you just have to show me how you do it to repeat what you saw. I cannot reproduce #12. -YY

Back to top