Changes

== What impact does the PFAN policy on conventional collective titles have on authority records in the case of partial compilations created after 1500? ==

== What impact does the PFAN policy on conventional collective titles have on authority records in the case of partial compilations created after 1500? ==

 

If a partial compilation created after 1500 includes a manifestation title that is recorded as a variant access point in an existing authority record for a conventional collective title, there are two options for resolving the conflict:

If a partial compilation created after 1500 includes a manifestation title that is recorded as a variant access point in an existing authority record for a conventional collective title, there are two options for resolving the conflict:

If  the variant access point in the existing authority record for a conventional collective title represents the same resource as the one being described (verify this by examining the 670 field that justifies the variant access point), delete the variant access point and the corresponding 670 field and describe the resource according to RDA 6.2.2.4.

 

<li>If  the variant access point in the existing authority record for a conventional collective title represents the same resource as the one being described (verify this by examining the 670 field that justifies the variant access point), delete the variant access point and the corresponding 670 field and describe the resource according to RDA 6.2.2.4.<br/>

Since the conventional collective title authority record is likely to be an undifferentiated work authority record, the record should not be recoded as RDA if it is not already. This is an exception to PFAN's policy that any authority record that is not RDA-coded must be recoded as RDA when it is modified in any way.

 

Since the conventional collective title authority record is likely to be an undifferentiated work authority record, the record should not be recoded as RDA if it is not already. This is an exception to PFAN's policy that any authority record that is not RDA-coded must be recoded as RDA when it is modified in any way.<br/>

If the record has not been evaluated and has no field 016, it is not necessary to evaluate it and add a unique Canadiana number. You can apply the procedure for partial modifications and add the generic number 1111X1111F.

 

If the record has not been evaluated and has no field 016, it is not necessary to evaluate it and add a unique Canadiana number. You can apply the procedure for partial modifications and add the generic number 1111X1111F.<br/>

Exception :  

If the variant access point that conflicts is the only variant listed in the record, and the 670 field that justifies this variant is the only 670 field in the record, leave the record unchanged and mark it for deletion.

Exception : <br/>

 

If the variant access point that conflicts is the only variant listed in the record, and the 670 field that justifies this variant is the only 670 field in the record, leave the record unchanged and mark it for deletion.</li>

(2) If the variant access point in the existing authority record for a conventional collective title does not represent the same resource as the one being described (for example, it may represent an earlier or later edition, or a completely different compilation of works), a 1XX/4XX conflict exists which must be resolved. A qualifier can be added to the conflicting 4XX. It is not necessary to recode the authority record as RDA if it is not already recoded. This is an exception to the PFAN policy that any authority record that is not RDA-coded must be recoded as RDA when  it is modified in any way.

 

<li>If the variant access point in the existing authority record for a conventional collective title does not represent the same resource as the one being described (for example, it may represent an earlier or later edition, or a completely different compilation of works), a 1XX/4XX conflict exists which must be resolved. A qualifier can be added to the conflicting 4XX. It is not necessary to recode the authority record as RDA if it is not already recoded. This is an exception to the PFAN policy that any authority record that is not RDA-coded must be recoded as RDA when  it is modified in any way.

If the record has not been evaluated and has no 016 field, it is not necessary to evaluate it and add a unique Canadiana number. You can apply the procedure for partial modifications and add the generic number 1111X1111F.

If the record has not been evaluated and has no 016 field, it is not necessary to evaluate it and add a unique Canadiana number. You can apply the procedure for partial modifications and add the generic number 1111X1111F.

 

Authority records can optionally be created if there is a conflict with another authorized access point in the “catalogue ”, i.e. the file in which searching and cataloging is carried out (e.g. the local catalogue, Canadiana, OCLC). Cataloguers can also take into account any resource with the same authorized access point and whose existence they are aware of, whether or not it appears in the catalogue. However, an authority record should not be created for the sole purpose of providing a variant access point comprising a conventional collective title. This would run counter to one of the policy objectives, which is to reduce the number of new authority records representing works.

Authority records can optionally be created if there is a conflict with another authorized access point in the “catalogue ”, i.e. the file in which searching and cataloging is carried out (e.g. the local catalogue, Canadiana, OCLC). Cataloguers can also take into account any resource with the same authorized access point and whose existence they are aware of, whether or not it appears in the catalogue. However, an authority record should not be created for the sole purpose of providing a variant access point comprising a conventional collective title. This would run counter to one of the policy objectives, which is to reduce the number of new authority records representing works.</li></div>

--->

--->