Kathy,

Y'all don't display 655s?

Elaine



J. Elaine Hardy
PINES & Collaborative Projects Manager
Georgia Public Library Service/PINES
1800 Century Place, Ste. 150
Atlanta, GA 30045

404.235.7128 Office
404.548.4241 Cell
404.235.7201 FAX

On Thu, Mar 16, 2017 at 11:01 AM, Kathy Lussier <kluss...@masslnc.org>
wrote:

> Hi all,
>
> In opac/parts/record/subjects.tt2, there is a line at the top of the file
> that indicates you're using the 650 MARC field for the subject links:
>
>     subjects = [
>         {
>             label => l('Subject: '),
>             xpath => '//*[@tag="600" or @tag="610" or @tag="611" or
> @tag="630" or @tag="650" or @tag="651"]'
>         },
>
> You can add indicators for that xpath if you want to limit the display to
> specific types of subject headings. For example, this is what's used at
> NOBLE to limit to LC and subject headings and LC headings for children:
>
>     subjects = [
>         {
>             label => l('Subject: '),
>             xpath => '//*[((@tag="600" or @tag="610" or @tag="611" or
> @tag="630" or @tag="650" or @tag="651") and (@ind2="0" or @ind2="1"))]'
>
> I hope this helps!
> Kathy
>
> On 03/16/2017 10:51 AM, Sarah Childs wrote:
>
> Ahem, Jason Boyer? Perhaps you could reveal how you have worked this
> magic?
>
> On Wed, Mar 15, 2017 at 6:23 PM, Jane Sandberg <sand...@linnbenton.edu>
> wrote:
>
>> We have been taking them out of our records.  Terry Reese's MarcEdit
>> program can generate FAST headings, so if we ever need them for
>> anything, we can export our bib records, work some MarcEdit magic on
>> them, and re-import them.
>>
>> Sarah, I'd be really curious how you were able to hide them from the
>> OPAC view, if you'd be willing to share!
>>
>>
>> On Wed, Mar 15, 2017 at 2:23 PM, Elaine Hardy
>> <eha...@georgialibraries.org> wrote:
>> > While we don't use them, we also don't take them out if they are in an
>> OCLC
>> > WorldCat record that is imported into our database. They are designed to
>> > work more readily with linked data than LCSH, so removing them now might
>> > mean adding them back later.
>> >
>> > We don't add them, either to records without them or to original input
>> in
>> > OCLC. OCLC does have a program that runs on a regular basis to add FAST
>> > headings to new cataloging, so they don't ask libraries to add them;
>> but,
>> > you can if you want.
>> >
>> > I have been intending exploring hiding them in the OPAC display since
>> they
>> > are duplicates, pretty much, of LCSH, but haven't had a chance. I do
>> also
>> > agree that they are messy.
>> >
>> > Elaine
>> >
>> >
>> >
>> > J. Elaine Hardy
>> > PINES & Collaborative Projects Manager
>> > Georgia Public Library Service/PINES
>> > 1800 Century Place, Ste. 150
>> > Atlanta, GA 30045
>> >
>> > 404.235.7128 Office
>> > 404.548.4241 Cell
>> > 404.235.7201 FAX
>> >
>> > On Wed, Mar 15, 2017 at 3:06 PM, Schooff, Rose (LVA)
>> > <rose.scho...@lva.virginia.gov> wrote:
>> >>
>> >> Libraries in our consortium (Virginia Evergreen Libraries) wanted me to
>> >> ask if you guys are using the FAST/searchFAST Subject Headings?
>> >>
>> >> Our libraries were saying that it creates a lot of duplication and
>> thought
>> >> it was messy, BUT what harm or damage would it cause in the future to
>> take
>> >> them out?
>> >>
>> >> Thanks for any replies.
>> >> —
>> >> Rose M. Schooff
>> >> Technology Consultant
>> >> Library Development and Networking
>> >> The Library of Virginia
>> >> 800 E. Broad Street
>> >> Richmond, VA  23219
>> >> 804-692-3772
>> >> 804-310-7901
>> >>
>> >
>>
>>
>>
>> --
>> Jane Sandberg
>> Electronic Resources Librarian
>> Linn-Benton Community College
>> sand...@linnbenton.edu / 541-917-4655
>> Pronouns: she/her/hers or they/them/theirs
>>
>
>
>
> --
> Sarah Childs
> Technical Services Department Head
> Hussey-Mayfield Memorial Public Library
> 250 North Fifth Street
> Zionsville, IN 46077
> 317-873-3149 x13330
> sar...@zionsvillelibrary.org
>
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative(508) 343-0128kluss...@masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>

Reply via email to