####### I.6 Publication, distribution, etc. area 

# I.6.1 Applicable rules

Per AACR2 12.4, record information about the place, name, and date of
all types of publishing, distributing, etc. activities as instructed in
AACR2 1.4. Use the 260 field for the publication/distribution
information. If the name of the publisher is already given in the title
proper or statement of responsibility, the cataloger should still repeat
the publisher name in the 260 field (older records may follow the
earlier AACR2 practice to shorten the name of the publisher).

Also follow AACR2 12.4.C2 (changes to place of publication,
distribution, etc.) and AACR2 12.4D2 (changes to name of publisher,
distributor, etc.). These rules specify that when the place or name of
publisher changes on a subsequent iteration, the place of publication
and/or publisher information is modified to reflect the information
appearing on the current iteration.

Dates are recorded following AACR2 12.4F1 which itself refers to the
general rule AACR2 1.4F. Important concepts in rule 1.4F8 include:

-   If cataloging is being done from the first published iteration, give
    the

> beginning date followed by a hyphen; if no date of publication,
> distribution, etc., or date of manufacture appears in the first
> published iteration, supply an approximate date of publication.

-   If cataloging is not being done from the first published iteration,
    do not give the beginning date (i.e., do not supply field 260 \$c)
    unless explicit information about the beginning date is found.
    Absent explicit information, give information about the beginning
    date in a note (see *I.6.2* and *I.9.9*).

-   In describing an integrating resource that is complete, give both
    the beginning and the ending date(s) of publication, separated by a
    hyphen, if this information is known for both the first and last
    iterations.

-   If cataloging is not being done from the first iteration, and no
    information is available about the beginning or ending date of
    publication, do not include field 260 subfield \$c and do not give a
    note (see AACR2 1.7B9 and 12.7B11.1). Do not supply the comma at end
    of field 260 subfield \$b if there is no subfield \$c.

The place and name of manufacturer and date of manufacture are also
recorded following AACR2 12.4G2b. If the data in these elements changes
on subsequent iterations, modify the 260 field to reflect the current
iteration and give the earlier place and/or name of manufacturer in a
note if considered to be important**.**

### I.6.2 PCC application/policy 

## 

LCRI 12.4D1 instructs the cataloger to apply the optional provision of
the rule and give the name of the distributor. Similarly, LCRI 12.4E
instructs the cataloger to apply general LCRI 1.4E and provide a
statement of function of publisher, distributor, etc. when needed to
clarify the role of two entities named in the publication/distribution
area.

The optional provision of AACR2 1.4.F8 allows the cataloger to supply
beginning and ending dates even if not cataloging from the first or last
iteration. Further, LCRI 1.4F8 instructs the cataloger to apply this
optional provision of the rule on a case-by-case basis when the
bibliographic resource includes an explicit statement, such as "Began in
1998". Give dates in square brackets in such a case. Generally, do not
investigate beyond the resource to find such a date.

![](media/image1.png){width="6.230555555555555in"
height="2.2493055555555554in"}

When making notes about changes that include dates, use angle brackets
when exact dates are unknown (see *I.9*).

## *I.6.2.1 Interim practice: Use notes for changes* 

The *MARC 21 Format for Bibliographic Data* defines the 260 field as
repeatable and lists specific indicator values for changes in
publication information. However, until MARC 21 changes to allow
repeatable 260 fields are implemented by library vendors, record earlier
place and publisher name information in a 500 note (see *I.9.10.1*). If
the publisher is also the issuing body, then give information about the
change in a 550 field (see *I.9.7*).

*I.6.2.2* *Future practice: Use of multiple 260 fields*

It is not yet clear how these changes in publication information will be
reflected in library system implementations in the long term. Therefore,
catalogers should not use multiple 260 fields or specific indicators as
defined in MARC 21, but should follow the interim practice noted above.

*I.6.3. Recording date information for updating loose-leafs*

Records for updating loose-leafs often contain notes citing probable
(i.e., inexact) dates because no exact dates are available in the item.
Enclose these probable dates in angle brackets.

##### 

##### 

##### 

##### I.9.3.3 Electronic resources

When examining an updating loose-leaf for dates, the cataloger often may
find a range of copyright dates, sometimes including previous editions
in the range. It may not be clear that the final date refers to the
specific edition or to the current iteration and further research may be
necessary.

Updating loose-leafs also undergo changes in the place and publisher.
For changes in the place or name of publisher, distributor, etc., place
or name of manufacturer, apply AACR2 12.4C2, 12.4D2 or 12.4G2. If any of
these elements change, change the description to reflect the current
iteration and give the information about earlier iterations in a note if
considered to be important per AACR 12.7B11.2 (see *I.9.7*).

###### I.6.4 Recording date information for electronic resources

Commonly, for remote access electronic resources, it is not known
whether the first iteration is being viewed. If it is determined that it
is not the first iteration, then the beginning date of publication is
not given unless there is explicit information elsewhere about the date
of the first iteration. If explicit information is not found, the
probable beginning date is recorded in notes (see *I.9*).

Explicit publication date information may appear on the home page, login
screen, menu, splash screen, etc., of a remote access electronic
resource or in communications with the publisher/producer/supplier of
the resource.

Examples of phrases that are considered explicit statements of
publication include:

Created in/on (date)

Institute mounted this page in (date)

Site no longer maintained after (date)

> First posted on (date)

Note that a single copyright date that appears on a later iteration of a
resource cannot be considered the beginning date, because it usually
indicates the current year. A single copyright date may be treated as a
possible date if no other information is available, and should be
recorded in a note (see *I.9*) rather than as field 260 subfield \$c.

Web sites often include many pieces of intellectual content that have
different copyright dates. Therefore, it is not clear when a range of
copyright dates or multiple copyright dates appear whether the first
date reflects the date of the site or the copyright date for the
content. Per LCRI 1.4F8, the first date in a range of dates (e.g.,
1999-2002) is not an explicit statement of the date of publication, but
it may be used to infer a possible beginning date. This date should be
recorded in a note (see *I.9.9*), not explicitly in field 260 subfield
\$c.

The final date in the range is not to be taken as an ending date for the
resource. That date just indicates the copyright continues to be held
and may be updated annually to reflect the latest year.

Notes about probable beginning dates use field 362 with the first
indicator coded "1". Records for integrating resources would never
contain a 362 field with the first indicator coded "0".

> ![](media/image2.png){width="4.382638888888889in"
> height="0.40625in"}![](media/image3.wmf){width="4.872916666666667in"
> height="0.5826388888888889in"}

###### 

###### 

###### 

###### 

###### 

###### 

###### 

###### 

###### 

###### 

###### I.6.4.1 When to transcribe date of publication

It will be less common to record a date in the field 260 \$c for
electronic resources, since catalogers seldom will be cataloging from
the first iteration (unless it is your institution that has actually
published the site). However, when working with an existing
bibliographic record that contains a beginning date in the field 260
\$c, accept the date as given.

# 1.6.5 Relationship of imprint information to fixed field 008

The current publication information recorded in the 260 field is the
basis of coding the dates in fixed field 008, bytes 7-10 and the place
of publication in fixed field 008, bytes 15-17 (see *I.13*). When the
place of publication changes on later iterations, the place of
publication must be updated in the 008. When the integrating resource is
complete, update the date information in the 008.