Search (7 results, page 1 of 1)

Parker, V.: MARC tags for cataloging cartographic materials (1999) 0.06

0.06113023 = product of:
  0.24452092 = sum of:
    0.24452092 = weight(_text_:fields in 5317) [ClassicSimilarity], result of:
      0.24452092 = score(doc=5317,freq=4.0), product of:
        0.31604284 = queryWeight, product of:
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.06382575 = queryNorm
        0.77369547 = fieldWeight in 5317, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.078125 = fieldNorm(doc=5317)
  0.25 = coord(1/4)

Abstract: This is a table of those MARC fields most frequently used when cataloging cartographic materials. The table gives fields both for monographs and for serials.

Riemer, J.J.: Adding 856 Fields to authority records : rationale and implications (1998) 0.04
```
0.042791158 = product of:
  0.17116463 = sum of:
    0.17116463 = weight(_text_:fields in 3715) [ClassicSimilarity], result of:
      0.17116463 = score(doc=3715,freq=4.0), product of:
        0.31604284 = queryWeight, product of:
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.06382575 = queryNorm
        0.5415868 = fieldWeight in 3715, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3715)
  0.25 = coord(1/4)
```
Abstract

Discusses ways of applying MARC Field 856 (Electronic Location and Access) to authority records in online union catalogues. In principle, each catalogue site location can be treated as the electronic record of the work concerned and the MARC Field 856 can then refer to this location as if it were referring to the location of a primary record. Although URLs may become outdated, the fact that they are located in specifically defined MARC Fields makes the data contained amenable to the same link maintenance software ae used for the electronic records themselves. Includes practical examples of typical union catalogue records incorporating MARC Field 856
Have, B.T.: Format integration : where are we? Report of the meeting of the ALCTS/LITA Serials Automation Interest Group, American Library Association, Midwinter Meeting, Los Angeles, February 1994 (1994) 0.04
```
0.03667814 = product of:
  0.14671256 = sum of:
    0.14671256 = weight(_text_:fields in 2396) [ClassicSimilarity], result of:
      0.14671256 = score(doc=2396,freq=4.0), product of:
        0.31604284 = queryWeight, product of:
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.06382575 = queryNorm
        0.4642173 = fieldWeight in 2396, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.046875 = fieldNorm(doc=2396)
  0.25 = coord(1/4)
```
Abstract

The topic was the implementation of format integration which will enalbe materials which have some aspect of seriality but could also be defined as another format, to be catalogues as both. An update of OCLC's format integration was given. The 1st phase, encompassing the changes to fields 010-8XX, will be complete by the end of 1994. The 2nd phase, which will contain changes to the 007 and 008 fields and the introduction of the 006 field, is scheduled for completion by the end 0f 1995. Local system vendors were supportive of format integration and changes to relevant programs were underway in preparation for implementation. In a discussion of conversion of pre-format integration records to format integration MARC it was felt that adequate staff and funding would not be available for massive conversion projects and that only selected records would be converted

Parent, I.: IFLA study on functional requirements for bibliographic records : an Anglo-American perspective (1995) 0.03

0.03458048 = product of:
  0.13832192 = sum of:
    0.13832192 = weight(_text_:fields in 3080) [ClassicSimilarity], result of:
      0.13832192 = score(doc=3080,freq=2.0), product of:
        0.31604284 = queryWeight, product of:
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.06382575 = queryNorm
        0.43766826 = fieldWeight in 3080, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.0625 = fieldNorm(doc=3080)
  0.25 = coord(1/4)

Abstract: Presents a view on the work of the Functional Requirements for Bibliographic Records Study Group on behalf of the Anglo-American cataloguing tradition. The study is examining the fundamental aspects of record design using the entity-attribute-relationship model to link data elements to the function that a user can perform while accessing a bibliographic record. The data and functions are being linked by UNIMARC fields

Fattahi, R.: ¬A uniform approach to the indexing of cataloguing data in online library systems (1997) 0.03
```
0.02593536 = product of:
  0.10374144 = sum of:
    0.10374144 = weight(_text_:fields in 131) [ClassicSimilarity], result of:
      0.10374144 = score(doc=131,freq=2.0), product of:
        0.31604284 = queryWeight, product of:
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.06382575 = queryNorm
        0.32825118 = fieldWeight in 131, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.951651 = idf(docFreq=849, maxDocs=44218)
          0.046875 = fieldNorm(doc=131)
  0.25 = coord(1/4)
```
Abstract

Argues that in library cataloguing and for optional functionality of bibliographic records the indexing of fields and subfields should follow a uniform approach. This would maintain effectiveness in searching, retrieval and display of bibliographic information both within systems and between systems. However, a review of different postings to the AUTOCAT and USMARC discussion lists indicates that the indexing and tagging of cataloguing data do not, at present, follow a consistent approach in online library systems. If the rationale of cataloguing principles is to bring uniformity in bibliographic description and effectiveness in access, they should also address the question of uniform approaches to the indexing of cataloguing data. In this context and in terms of the identification and handling of data elements, cataloguing standards (codes, MARC formats and the Z39.50 standard) should be brought closer, in that they should provide guidelines for the designation of data elements for machine readable records

Ranta, J.A.: Queens Borough Public Library's Guidelines for cataloging community information (1996) 0.02

0.015133139 = product of:
  0.060532555 = sum of:
    0.060532555 = weight(_text_:22 in 6523) [ClassicSimilarity], result of:
      0.060532555 = score(doc=6523,freq=2.0), product of:
        0.2235069 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.06382575 = queryNorm
        0.2708308 = fieldWeight in 6523, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=6523)
  0.25 = coord(1/4)

Source: Cataloging and classification quarterly. 22(1996) no.2, S.51-69

Crook, M.: Barbara Tillett discusses cataloging rules and conceptual models (1996) 0.02

0.015133139 = product of:
  0.060532555 = sum of:
    0.060532555 = weight(_text_:22 in 7683) [ClassicSimilarity], result of:
      0.060532555 = score(doc=7683,freq=2.0), product of:
        0.2235069 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.06382575 = queryNorm
        0.2708308 = fieldWeight in 7683, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=7683)
  0.25 = coord(1/4)

Source: OCLC newsletter. 1996, no.220, S.20-22

Search (7 results, page 1 of 1)

Authors

Themes