disable PICA download on enter in metadata fields

Registered by Ralf Claussnitzer on 2011-11-28

As a source of confusion in process creation form, hitting enter in text fields triggers download of meta data from PICA catalogue. This might overwrite existing field values or provide incorrect information if PICA number is not actually correct.

An approach to the problem could be disabling the <enter> key in this particular form, or to enhance validation rules. Disabling the enter key requires JavaScript and might raise browser compatibility issues.

FORM submission and the ENTER key? http://www.alanflavell.org.uk//www/formquestion.html

Blueprint information

Status:
Complete
Approver:
None
Priority:
Low
Drafter:
None
Direction:
Approved
Assignee:
Henning Gerhardt
Definition:
Approved
Series goal:
Accepted for 1.8
Implementation:
Implemented
Milestone target:
milestone icon 1.8.0
Started by
Ralf Claussnitzer on 2012-07-30
Completed by
Ralf Claussnitzer on 2012-07-30

Whiteboard

This problem is addressed by the <tr:form> attribute defaultCommand.
See: http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_form.html
--
Matthias Ronge, Zeutschel

Can you provide a patch?

--
In-House (SLUB DD) preferred solution: enter key should work on ppn / opac query input field but should not generate any action if used in other input fields. For example: entering PPN digital happend for journals with a bar code scanner which sends after required data an enter key. This submitted enter key caused the trouble descripted in the blue print.

(?)

Work Items

Work items:
Provide patch: TODO
Check with users: TODO

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.