Re: [Koha] Journal articles and analytical records
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@mdah.state.ms.us> Subject: [Koha] Journal articles and analytical records To: koha <koha@lists.katipo.co.nz> Message-ID: <4BACB35A.6060505@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@numismatics.org> Subject: Re: [Koha] Journal articles and analytical records To: Linda Culberson <lculber@mdah.state.ms.us> Cc: koha <koha@lists.katipo.co.nz> Message-ID: <4BACC9CD.8050608@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
-- Elaine
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@mdah.state.ms.us> Subject: [Koha] Journal articles and analytical records To: koha<koha@lists.katipo.co.nz> Message-ID:<4BACB35A.6060505@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@numismatics.org> Subject: Re: [Koha] Journal articles and analytical records To: Linda Culberson<lculber@mdah.state.ms.us> Cc: koha<koha@lists.katipo.co.nz> Message-ID:<4BACC9CD.8050608@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@ptfs-europe.com
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@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@mdah.state.ms.us> Subject: [Koha] Journal articles and analytical records To: koha<koha@lists.katipo.co.nz> Message-ID:<4BACB35A.6060505@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@numismatics.org> Subject: Re: [Koha] Journal articles and analytical records To: Linda Culberson<lculber@mdah.state.ms.us> Cc: koha<koha@lists.katipo.co.nz> Message-ID:<4BACC9CD.8050608@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@ptfs-europe.com
-- Elaine
Elaine, If you index serials, using 774s will probably push at least some of your records beyond the 99999-character limit set by MARC21. We haven't really worried about parent->child links yet, but what I had in mind was adding an "indexed" flag of some sort to the parent record, and then offering a search on the OPAC. Like so: Child record: =773 \\$tCataloging & Classification Quarterly$x0163-9374$gVol. 38, no. 1 (2004) Parent record (the 997$x is ANS local-use): =022 \\$a0163-9374 =245 \\$aCataloging & Classification Quarterly =997 \\$x1 In the OPAC: If 997$x==1 Then: <a href="opac-search.pl?q=issn:022">Search for child records</a> This would require defining the issn: operator in Zebra to search 773$x. We haven't implemented this yet, of course, but that's how I imagine it working. It's not ideal, since we wouldn't really be able to limit the search to a single issue (except in annual journals, of course, when we could just limit by year), but it's better than nothing. All very speculative, but one needs something to think about to stave off hopelessness when adding 773$x and 773$z to tens of thousands of records. Regards, Jared Camins-Esakov Elaine wrote:
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
Indeed We decided against listing the individual articles in the parent record if it's a serial. It would be overwhelming to the reader and cataloger alike. Our main use for 774 would be conference proceedings, or chapters in a book of collected essays, etc. However, with your linking system, it could be possible to browse through the other child records, and less overwhelming than a whole screen or three of 774 fields. Elaine On Mon, Mar 29, 2010 at 3:07 PM, <camins@numismatics.org> wrote:
Elaine,
If you index serials, using 774s will probably push at least some of your records beyond the 99999-character limit set by MARC21. We haven't really worried about parent->child links yet, but what I had in mind was adding an "indexed" flag of some sort to the parent record, and then offering a search on the OPAC. Like so:
Child record: =773 \\$tCataloging & Classification Quarterly$x0163-9374$gVol. 38, no. 1 (2004)
Parent record (the 997$x is ANS local-use): =022 \\$a0163-9374 =245 \\$aCataloging & Classification Quarterly =997 \\$x1
In the OPAC: If 997$x==1 Then: <a href="opac-search.pl?q=issn:022">Search for child records</a>
This would require defining the issn: operator in Zebra to search 773$x.
We haven't implemented this yet, of course, but that's how I imagine it working. It's not ideal, since we wouldn't really be able to limit the search to a single issue (except in annual journals, of course, when we could just limit by year), but it's better than nothing. All very speculative, but one needs something to think about to stave off hopelessness when adding 773$x and 773$z to tens of thousands of records.
Regards, Jared Camins-Esakov
Elaine wrote:
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
-- Elaine
Hi all We use Koha for cataloguing articles. Since these records are exported to Vufind (OpenURL), the linkage isn't an issue for our purposes so far. Maybe our experiences are helpful for other Koha users anyway. By now we have 400 Journals. - First thing we did, is to create a default “Article” MARC framework with basic values already filled in (000, 008, 245 for punctuation, 773) - Since we need OpenURL, we expanded the tags for the 773 field according to : http://www.loc.gov/marc/marbi/2003/2003-dp01.html (Section 4.1) __ <http://www.loc.gov/marc/marbi/2003/2003-dp01.html> - We have a csv list with our Journals and the according ISSN. From (MySQL) biblio_framework we created templates for the 400 Journals with Jounal title and ISSN already filled in. Problems and Solutions: - Inside Koha it is quite difficult to find the right Journal out of 400 existing templates. Since we are using Drupal for Extranet and Intranet we created a list of our journals with a direct link to the Koha template (any other CMS might do as well ;-). - Since our databese is collaborative, some institutions are using IE. The advanced tag editor for 000 and 008 is not opening with IE. Undo the spaces in marc21_field_008_authorities.pl and marc21_field_008.pl in the UNIMARC section (Bug reported). - Still in the 008, the country and language code are not in the correct place. By consequence Vufind was not able to allocate country and language from the 008 tag. Again this must be correctes in the marc21_field_008.pl to 080602s2008(4)gw(12)00(4)ger(1)d (where the numbers in brackets are the number of spaces to be filled in) By now we have no solution for following problem: - Our 773 subfield structure allows only to display the startpage. We need to get the endpage OpenURL readable as well. The built in OpenURL module of Koha toghether with DAIA : http://www.gbv.de/wikis/cls/Document_Availability_Information_API_(DAIA) <DAIA> would be a great All in One solution for our purposes. If someone has similar interests, please give a sign. Greetings, Stefan
I have no answers, but I do have a suggestion and a question. First, you might want to take a look at the Journal Articles thread on this list where people are talking about a similar topic: http://lists.katipo.co.nz/pipermail/koha/2010-March/thread.html#23186 My question is did you report a bug for your 008 country/language issue? I ask because you said you reported a bug for the one before, but not that one. If not, that is most certainly a bug and you should report it. Thanks Nicole C. Engard On Sat, Apr 17, 2010 at 12:28 AM, stefan <herrkandera@gmx.ch> wrote:
Hi all
We use Koha for cataloguing articles. Since these records are exported to Vufind (OpenURL), the linkage isn't an issue for our purposes so far. Maybe our experiences are helpful for other Koha users anyway.
By now we have 400 Journals.
- First thing we did, is to create a default “Article” MARC framework with basic values already filled in (000, 008, 245 for punctuation, 773)
- Since we need OpenURL, we expanded the tags for the 773 field according to : http://www.loc.gov/marc/marbi/2003/2003-dp01.html (Section 4.1) __ <http://www.loc.gov/marc/marbi/2003/2003-dp01.html> - We have a csv list with our Journals and the according ISSN. From (MySQL) biblio_framework we created templates for the 400 Journals with Jounal title and ISSN already filled in.
Problems and Solutions:
- Inside Koha it is quite difficult to find the right Journal out of 400 existing templates. Since we are using Drupal for Extranet and Intranet we created a list of our journals with a direct link to the Koha template (any other CMS might do as well ;-).
- Since our databese is collaborative, some institutions are using IE. The advanced tag editor for 000 and 008 is not opening with IE. Undo the spaces in marc21_field_008_authorities.pl and marc21_field_008.pl in the UNIMARC section (Bug reported).
- Still in the 008, the country and language code are not in the correct place. By consequence Vufind was not able to allocate country and language from the 008 tag. Again this must be correctes in the marc21_field_008.pl to 080602s2008(4)gw(12)00(4)ger(1)d (where the numbers in brackets are the number of spaces to be filled in)
By now we have no solution for following problem:
- Our 773 subfield structure allows only to display the startpage. We need to get the endpage OpenURL readable as well.
The built in OpenURL module of Koha toghether with DAIA : http://www.gbv.de/wikis/cls/Document_Availability_Information_API_(DAIA) <DAIA>
would be a great All in One solution for our purposes. If someone has similar interests, please give a sign.
Greetings, Stefan
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Thank you Nicole I did not post the 008 country/language bug, since my solution is not working properly (it's more like a workaround for now). I think some modification in the marc21_field_008.tmpl is needed as well. I will report, once solved. Regards, Stefan Nicole Engard schrieb:
I have no answers, but I do have a suggestion and a question.
First, you might want to take a look at the Journal Articles thread on this list where people are talking about a similar topic: http://lists.katipo.co.nz/pipermail/koha/2010-March/thread.html#23186
My question is did you report a bug for your 008 country/language issue? I ask because you said you reported a bug for the one before, but not that one. If not, that is most certainly a bug and you should report it.
Thanks Nicole C. Engard
On Sat, Apr 17, 2010 at 12:28 AM, stefan <herrkandera@gmx.ch> wrote:
Hi all
We use Koha for cataloguing articles. Since these records are exported to Vufind (OpenURL), the linkage isn't an issue for our purposes so far. Maybe our experiences are helpful for other Koha users anyway.
By now we have 400 Journals.
- First thing we did, is to create a default “Article” MARC framework with basic values already filled in (000, 008, 245 for punctuation, 773)
- Since we need OpenURL, we expanded the tags for the 773 field according to : http://www.loc.gov/marc/marbi/2003/2003-dp01.html (Section 4.1) __ <http://www.loc.gov/marc/marbi/2003/2003-dp01.html> - We have a csv list with our Journals and the according ISSN. From (MySQL) biblio_framework we created templates for the 400 Journals with Jounal title and ISSN already filled in.
Problems and Solutions:
- Inside Koha it is quite difficult to find the right Journal out of 400 existing templates. Since we are using Drupal for Extranet and Intranet we created a list of our journals with a direct link to the Koha template (any other CMS might do as well ;-).
- Since our databese is collaborative, some institutions are using IE. The advanced tag editor for 000 and 008 is not opening with IE. Undo the spaces in marc21_field_008_authorities.pl and marc21_field_008.pl in the UNIMARC section (Bug reported).
- Still in the 008, the country and language code are not in the correct place. By consequence Vufind was not able to allocate country and language from the 008 tag. Again this must be correctes in the marc21_field_008.pl to 080602s2008(4)gw(12)00(4)ger(1)d (where the numbers in brackets are the number of spaces to be filled in)
By now we have no solution for following problem:
- Our 773 subfield structure allows only to display the startpage. We need to get the endpage OpenURL readable as well.
The built in OpenURL module of Koha toghether with DAIA : http://www.gbv.de/wikis/cls/Document_Availability_Information_API_(DAIA) <DAIA>
would be a great All in One solution for our purposes. If someone has similar interests, please give a sign.
Greetings, Stefan
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Rather than start a new wiki, perhaps sub-pages under cataloging or serials on the existing wiki? Lenora A. Oftedahl StreamNet Regional Librarian Columbia River Inter-Tribal Fish Commission http://www.fishlib.org
participants (6)
-
camins＠numismatics.org -
Elaine Bradtke -
Ian Bays -
Lenora Oftedahl -
Nicole Engard -
stefan