[Koha] Journal articles and analytical records

[Elaine Bradtke]

We're looking at using 774 - Constituent Unit Entry to link from the
parent to each child. Not sure if we'll implement it, as it requires a
lot of extra data entry that hasn't been done.  We've already got
records for the children (with the information on the parent item),
and the parents, but not the details of all the children in the parent
records.    Right now it's more important for us to link upwards to
the parent item so you can actually find the physical item.
Elaine
On Mon, Mar 29, 2010 at 2:25 PM, Ian Bays <ian.bays at ptfs-europe.com> wrote:
> Hi Elaine,
> We are using the "link" within the MARC framework (subfield, edit subfields,
> select subfield, display more constraints, Link) in tag 776 (Additional
> Physical Form Entry) to link to other records.  We set this in subfield 'o'
> to 'Control-number' which equates in Zebra terms to the 001 tag.  We loaded
> accession numbers in the 001 tags.  This seems to work (version 3.01.00.061)
> but is quite limited in where you can see the link work.  Out of the box you
> can only see the link work in the staff client when looking at the MARC view
> of the detail record.  In this case you can click on the hyperlink and you
> are taken to the other record, but as yet I do not see it in the OPAC.
>  Maybe the 773 OPAC display might be more inclusive and have the links.  We
> will probably be looking more at these linkages for this and other
> customers.
>
> What you describe below looks good for potentially linking from the child to
> the parent record, but I am not sure how you would link from parent to
> child.
>
> I hope this may be of some use to you.
> All the best.
> Ian
> Keep the list posted if you make any progress.
> On 29/03/2010 12:27, Elaine Bradtke wrote:
>>
>> Regarding the subfields in 773, I'm using $x  ISSN and $z ISBN when we
>> have this information, plus $o for the accession number of the item. A
>> lot of what we have doesn't have  International Standard numbers for
>> one reason or another, but it all has an accession number.
>> I haven't worried too much about the display at the moment, it seemed
>> to look ok in the test runs.
>> The one thing I couldn't get to function was a link between the 773
>> field and the parent item, but we're a bit behind in installing Koha
>> releases*, and this may work better in the newer ones.
>>
>> Perhaps we should form a group on analytics and pool our information
>> and techniques?  With an idea of putting together a little wiki?
>>
>> Thanks
>> Elaine
>> (*I work 2 days a week on this project, and my IT guru is a volunteer. . .
>> )
>>
>>
>>>
>>> Message: 3
>>> Date: Fri, 26 Mar 2010 08:15:06 -0500
>>> From: Linda Culberson<lculber at mdah.state.ms.us>
>>> Subject: [Koha]  Journal articles and analytical records
>>> To: koha<koha at lists.katipo.co.nz>
>>> Message-ID:<4BACB35A.6060505 at mdah.state.ms.us>
>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>
>>> All,
>>> We are just now loading our records, but have thousands of analytic
>>> records that we will be experimenting with. Like Elaine and Beda, we are
>>> looking at using the 773.  I was thinking about putting the host item
>>> system number in the subfield $w and maybe using the subfield $o for
>>> something to tie directly to the individual item. In our current system
>>> we are using the item part, and I was thinking of either trying that or
>>> using the barcode or itemnumber in the $o. What subfields have been used
>>> in your testing, Elaine?
>>>
>>> I am relieved to know we are not alone in looking at this and look
>>> forward to working with everyone.  We have absolutely no funds to
>>> contribute but sweat equity works, I hope.
>>>
>>> Thanks!
>>>
>>> Linda
>>>
>>
>>
>>>
>>> Message: 5
>>> Date: Fri, 26 Mar 2010 10:50:53 -0400
>>> From: Jared Camins-Esakov<camins at numismatics.org>
>>> Subject: Re: [Koha] Journal articles and analytical records
>>> To: Linda Culberson<lculber at mdah.state.ms.us>
>>> Cc: koha<koha at lists.katipo.co.nz>
>>> Message-ID:<4BACC9CD.8050608 at numismatics.org>
>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>
>>> Good morning, list,
>>>
>>> I replied off-list to Andrew yesterday, assuming that no one else was
>>> crazy enough to create analytics, but it looks like I was wrong.
>>>
>>> In our database of ~175,000 bibliographic records, we have ~120,000
>>> analytic records, created over the last 50 years (our card catalog was
>>> digitized in the 90s). Our old system did not link analytics, but we
>>> very much want to provide linking in the new Koha catalog. I added
>>> ISBNs, ISSNs, LCCNs, and local control numbers to ~91,000 of those
>>> analytic records, but for everything except for the ISBN, that only
>>> identifies the bibliographic record and not the actual item. We don't
>>> currently do anything with the links, although it seems like it
>>> shouldn't be too problematic to add them, at least on a bib record level
>>> (50 years of catalogers have resulted in exceedingly inconsistent 773$g
>>> formatting).
>>>
>>> It's very good to know that we're not going it alone with regards to
>>> analytic records in Koha. How are those of you with analytics displaying
>>> host publication information in the OPAC?
>>>
>>> Unfortunately, we probably don't have any money for sponsoring these
>>> features, either.
>>>
>>> Regards,
>>> Jared
>>>
>>>
>>
>>
>>
>>
>
>
> --
> Ian Bays
> Director of Projects
> PTFS Europe.com
> mobile: +44 (0) 7774995297
> phone: +44 (0) 800 756 6803
> skype: ian.bays
> email: ian.bays at ptfs-europe.com
>
>



-- 
Elaine