[OPEN-ILS-GENERAL] Is 264 field indexed and visible in 2.5 version?

[Ben Shum]

Hi Trisha and Yamil,

For clarification, tag 264 for *publisher* data was developed and part of
Evergreen 2.4 and was subsequently backported to 2.2.9 and 2.3.7 as well
(see https://bugs.launchpad.net/evergreen/+bug/1071505).  Indexing
publisher information has not been done to my knowledge by default.  We did
update the reporter view to include tag 264 for pubdate (publisher date) so
any reports that draw from publication info reflects either 260 or 264 for
publisher data.

The bug that Yamil references deals with other forms of tag 264 for
"Producer, Distributor, Manufacturer, and Copyright" which is noted in the
bug's description.  Differentiating between the types of tag 264 is done
through the indicator fields.  The other issue Yamil mentions with
https://bugs.launchpad.net/evergreen/+bug/1304462 and the search results is
actually a bug that needs to be addressed as well.  Right now, it's
grabbing and displaying any 264 found and potentially mislabeling it as
"publisher" in search results when in fact it could be other things.
 Resolving this bug and completing the work for RDA 264 is on my personal
short list of code to finish for Evergreen 2.7.0-beta1 next Thursday.  Good
to get a nudge, thanks Yamil.  ;)

-- Ben




On Thu, Jul 31, 2014 at 4:13 PM, Yamil Suarez <ysuarez at berklee.edu> wrote:

> Trisha,
>
> As far as I know, and I could be wrong, no version of EG supports the
> displaying the (RDA) 264 tag. Jason Stephenson, from MVLC, wrote some
> code that takes care of displaying the 264 data on the OPAC for the
> full bib display. That code change has not been officially approved to
> be added to EG yet. His code inspired a nice debate on how to move
> forward with some related RDA and 264 issues, and I guess momentum was
> lost. For example, at the time he made his changes public there was a
> debate of how to tweak his changes or repurpose his code logic to
> allow non-publisher data to show up in the search results. Though
> Jason's code seem to perfectly handle the 264 data in the full bib
> view, and I have since added his code to my EG 2.5 system.
>
> Add 264 tag values to Record Summary
> https://bugs.launchpad.net/evergreen/+bug/1304462
>
> Here is a link to the changes he made to make the 264 data show up in
> the full bib view...
>
> http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=9cf41dc26c536000dcd1cfe52fdf430accb63093
>
> At this point I am not sure what the status is of searching (indexing)
> on the 264 tag.
>
> Coincidentally I was just reviewing Jason's code this week, so I can I
> try to help revive his code and help propose additional RDA related
> code changes.
>
> I hope this helps,
> Yamil
>
>
> On Thu, Jul 31, 2014 at 3:49 PM, Trisha Cantwell Keene
> <tcantwell at coa.edu> wrote:
> >
> > Are folks still utilizing the 260 for publication/distributor
> information or
> > can we now use 264?
> >
> > Thanks
> > Trisha
> > --
> > Trisha Cantwell Keene
> > Associate Director
> > Thorndike Library
> > College of the Atlantic
> > 109 Eden St.
> > Bar Harbor, ME  04609
> >
> > (207) 801-5661
> > (207) 288-2328 Fax
> > tcantwell at coa.edu
> >
> > "Google can bring you back a hundred thousand answers. A librarian can
> > bring you back the right one."  The Guardian (London)
>
>
>
> --
>
>
>
> --------------------------------
>
> Yamil Suarez, MCS
> Library System Administrator/Developer
>
> Stan Getz Library
> Berklee College of Music
> 1140 Boylston St
> Boston, MA 02215
>
> ysuarez at berklee.edu
> 617-747-2617
>



-- 
Benjamin Shum
Evergreen Systems Manager
Bibliomation, Inc.
24 Wooster Ave.
Waterbury, CT 06708
203-577-4070, ext. 113
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20140731/c688395a/attachment-0001.htm>