New field that new imported records will be tagged with on the import action, so as to monitor and be easily identifiable when searching. It can be a field assigned on the backend on import or a specific metadata field with a value.
If no record is selected and then click "Submit Selected Records" the Message that should be shown is: No record was selected and imported!
Not clear heading Unmatched heading -> use Heading doesn’t exist
I receive Fatal: 191$b Ambiguous heading: E/ESCWA/
. Additional specification should probably be set.
Authority 191 $bE/ESCWA/
exists, so I shouldn't have received the "Ambiguous heading". This is a valid value just with the b!
This occurs because we have additional c value like for example in the following:
E/ESCWA/
E/ESCWA/; 26
E/ESCWA/; 25
->No message "Ambiguous heading"/ Please adjust code to select the valid value (one without c). If it has a c field then the one with b and c.
5.New auths can be imported - Expected behavior and user stories need to be identified and discussed - no specs.
I imported a duplicate one -no message received, created a bib with the link to its duplicate
1373594
887673
New field that new imported records will be tagged with on the import action, so as to monitor and be easily identifiable when searching. It can be a field assigned on the backend on import or a specific metadata field with a value.
If no record is selected and then click "Submit Selected Records" the Message that should be shown is: No record was selected and imported!
Not clear heading Unmatched heading -> use Heading doesn’t exist
I receive Fatal: 191$b Ambiguous heading: E/ESCWA/ . Additional specification should probably be set.
Authority 191 $bE/ESCWA/ exists, so I shouldn't have received the "Ambiguous heading". This is a valid value just with the b! This occurs because we have additional c value like for example in the following: E/ESCWA/ E/ESCWA/; 26 E/ESCWA/; 25 ->No message "Ambiguous heading"/ Please adjust code to select the valid value (one without c). If it has a c field then the one with b and c.
5.New auths can be imported - Expected behavior and user stories need to be identified and discussed - no specs. I imported a duplicate one -no message received, created a bib with the link to its duplicate 1373594 887673