Am 2013-10-20 um 04:32 schrieb Tibor Simko <[email protected]>: > On Mon, 14 Oct 2013, [email protected] wrote: >> We resolved to several lines with the same key code. > > This is a good strategy. Though, looking at your examples, you may > perhaps want to be more specific in some cases:
As I wrote, these records were generated automatically and contain errors. >> DATE 2005-08-14 >> DATE 2013-03-13T12:07:30.288832+00:00 > > DATE_CREATION vs DATE_MODIFICATION? No. There should be always just one DATE line, and it’s defined as publishing date (or recording date of audio/video files, if the publishing date is unknown). >> TITLE 16527 >> TITLE 1001 задача для умственного счета > > TITLE_EN vs TITLE_RU? No. The first one is actually a REFNO. Most of our media is unilingual, the language to be defined as LANG. We would need distinct key codes for every language (about 5) and every field - please, no… If we would need to mark the language of a single field, I’d use a marker like <LANG: rus>. If a book has several titles of the same level, like a Kyrgyz and a Russian title, we just save both without added metadata - users will find the title in both languages, that’s enough. Thank you for your comments, though. Greetlings, Hraban --- http://www.fiee.net https://www.cacert.org (I'm an assurer)
