We could add an ON CREATE trigger on biblio.record_entry to set the first six characters of 008 (if it exists in the record - I'm not sure we want to get into the business of creating 008 fields from scratch) by invoking to_char(create_date, 'YYMMDD') to get the properly formatted version of the date.
This is probably something we should have in place out of the box; it's a relatively small piece of work for an additional standards compliance checkmark. Mieke, would you mind adding a wishlist item on this point to http://bugs.launchpad.net/evergreen ? Dan On Sat, Jun 25, 2011 at 10:51 AM, Joel Harbottle <[email protected]> wrote: > Hi Mieke, > > I know with the 008 tag in Evergreen you can click on the line and highlight > the 070101 and change it to the current date, e.g., 110625, and then just > complete the 008 tag as you normally would, either directly in the text of > the tag, or via the table/grid at the top of the MARC Editor screen. > > I hope this helps. > > Kindest Regards, > Joel > > > ________________________________ >> From: Mieke Stroo <[email protected]> >> Reply-To: Evergreen Discussion Group >> <[email protected]> >> Date: Thu, 23 Jun 2011 14:41:56 +0200 >> To: Evergreen Discussion Group >> <[email protected]> >> Subject: [OPEN-ILS-GENERAL] 008 field and leader >> >> Hi all, >> >> The IISG in Amsterdam is running EG 2.0.3. We noticed that the 008 field >> always starts with 070101, presumably January first 2007. Could anyone >> tell us >> how to have this date changed automatically when entering a new record? Is >> it >> possible to have a computer generated date in this field? >> >> The positions 0-4 and 12-16 in the leader are unclear to us. According to >> the >> MARC 21 standard this information should be computer generated. Is it >> alright >> to use a set number (00620) for the positions 0-4 and leave the positions >> 12-16 open? >> >> Mieke Stroo >> >> IISG >> Postbus 2169 >> 1000 CD Amsterdam >> The Netherlands >> >> [email protected] >> >> >> >> >> >
