Line 80: |
Line 80: |
| No, the creation or revision of series authority records is not yet allowed in the Canadiana file. This will not be possible until the training documentation on Series authorities has been created. | | No, the creation or revision of series authority records is not yet allowed in the Canadiana file. This will not be possible until the training documentation on Series authorities has been created. |
| | | |
− | == <span style="color:red">When a corporate body has gone through a name change, or several name changes, and there are authority records, in Canadiana, for the other names, which relationships should be recorded in an authority record (field 5XX)? In which cases should cataloguers revise the authority records for those related corporate bodies? == | + | == When a corporate body has gone through a name change, or several name changes, and there are authority records, in Canadiana, for the other names, which relationships should be recorded in an authority record (field 5XX)? In which cases should cataloguers revise the authority records for those related corporate bodies? == |
| | | |
− | <span style="color:red">Cataloguers should record only two types of sequential relationships: the corporate body's name immediately preceding the one the cataloguers are working on, and the one immediately following it, if applicable. These are prescribed in the [[PFAN_-_PFAN_Policy_Statements#32.1.2C_Related_Corporate_Body_.5BNew.5D|PFAN PS for 32.1]], which states that the element “Related corporate bodies” is a core element for sequential relationships with immediately preceding and immediately succeeding corporate bodies (conferences being the exception).
| + | Cataloguers should record only two types of sequential relationships: the corporate body's name immediately preceding the one the cataloguers are working on, and the one immediately following it, if applicable. These are prescribed in the [[PFAN_-_PFAN_Policy_Statements#32.1.2C_Related_Corporate_Body_.5BNew.5D|PFAN PS for 32.1]], which states that the element “Related corporate bodies” is a core element for sequential relationships with immediately preceding and immediately succeeding corporate bodies (conferences being the exception). |
| | | |
− | <span style="color:red">If the authority record for one or another of these corporate bodies is coded RDA or is “RDA acceptable” (in other terms, is coded AACR2, but displays an authorized access point which would be constructed in the same way according to RDA and applicable policy statements), it is not necessary to revise the record for this AAP, even if this is a migrated record which has not been reassessed.
| + | If the authority record for one or another of these corporate bodies is coded RDA or is “RDA acceptable” (in other terms, is coded AACR2, but displays an authorized access point which would be constructed in the same way according to RDA and applicable policy statements), it is not necessary to revise the record for this AAP, even if this is a migrated record which has not been reassessed. |
| | | |
− | <span style="color:red">If the authority record for one or another of these corporate bodies is neither RDA nor “RDA acceptable”, both the AAP and the entire authority record must be revised, and the record's coding will be changed to RDA.
| + | If the authority record for one or another of these corporate bodies is neither RDA nor “RDA acceptable”, both the AAP and the entire authority record must be revised, and the record's coding will be changed to RDA. |
| | | |
− | <span style="color:red">''Examples:'' <br>
| + | ''Examples:'' <br> |
| 1) A cataloguer is creating an authority record for corporate body C, which was formerly called A and then B in the past. The authority records for A and B are “RDA acceptable”. The cataloguer will add a 5XX in record C, recording a sequential relationship to B, but there is no need to revise B's authority record. <br> | | 1) A cataloguer is creating an authority record for corporate body C, which was formerly called A and then B in the past. The authority records for A and B are “RDA acceptable”. The cataloguer will add a 5XX in record C, recording a sequential relationship to B, but there is no need to revise B's authority record. <br> |
− | 2) A cataloguer is revising the authority record for corporate body D, which was formerly called A, B and C in the past, and was later called E and F. The authority record for body C is “RDA acceptable”, and the record for body E is coded RDA. The cataloguer will add two 5XX in the authority for body D, recording relationships with bodies C and E, but there is no need to revise the authority records for C and E. <br> </span> | + | 2) A cataloguer is revising the authority record for corporate body D, which was formerly called A, B and C in the past, and was later called E and F. The authority record for body C is “RDA acceptable”, and the record for body E is coded RDA. The cataloguer will add two 5XX in the authority for body D, recording relationships with bodies C and E, but there is no need to revise the authority records for C and E. <br> |
| | | |
− | == <span style="color:red">How do I determine the usage for an agent name in WMS?</span>== | + | == How do I determine the usage for an agent name in WMS?== |
| | | |
− | <span style="color:red">To determine the name by which an agent is commonly known or identified, RDA asks you first to consult the preferred sources of information in the events associated with the agent. To do this, we recommend checking usage in the WorldCat database. The Name Authority Manual defines "usage" as "the transcribed forms of names usually found in bibliographic record statements of responsibility." The Guide also states that "these forms may also be found in other parts of the bibliographic record, such as the title proper or a cited note." </span>
| + | To determine the name by which an agent is commonly known or identified, RDA asks you first to consult the preferred sources of information in the events associated with the agent. To do this, we recommend checking usage in the WorldCat database. The Name Authority Manual defines "usage" as "the transcribed forms of names usually found in bibliographic record statements of responsibility." The Guide also states that "these forms may also be found in other parts of the bibliographic record, such as the title proper or a cited note." |
| | | |
− | <span style="color:red">Checking usage in WorldCat is not necessarily an easy task. Although there are no strict established procedures, the Standards Committee suggests the following the guidelines.</span>
| + | Checking usage in WorldCat is not necessarily an easy task. Although there are no strict established procedures, the Standards Committee suggests the following the guidelines. |
| | | |
− | <span style="color:red">The search can first be carried out in French-language bibliographic records. Quite often, however, the French records do not offer a sufficiently representative sample to determine with certainty the name by which an agent is commonly known or identified. In such cases, it may be useful to consult bibliographic records in English. In this case, it is not necessary to note in a 670 field the authorized access points appearing in the English records, unless they are needed to justify access point variants.</span>
| + | The search can first be carried out in French-language bibliographic records. Quite often, however, the French records do not offer a sufficiently representative sample to determine with certainty the name by which an agent is commonly known or identified. In such cases, it may be useful to consult bibliographic records in English. In this case, it is not necessary to note in a 670 field the authorized access points appearing in the English records, unless they are needed to justify access point variants. |
| | | |
− | <span style="color:red">As for the scope of your search, it's best not to limit yourself to your own collection, but to search the whole of WorldCat. That said, searching for usage is not particularly user-friendly in WMS. Instead, we recommend using the browser [http://connexion.oclc.org/ Connexion], which allows you to consult directly in the search results screen, once the "Brief list" view has been selected. It should be noted that an enhancement request has been made so that this display is also available in WMS.</span>
| + | As for the scope of your search, it's best not to limit yourself to your own collection, but to search the whole of WorldCat. That said, searching for usage is not particularly user-friendly in WMS. Instead, we recommend using the browser [http://connexion.oclc.org/ Connexion], which allows you to consult directly in the search results screen, once the "Brief list" view has been selected. It should be noted that an enhancement request has been made so that this display is also available in WMS. |
| <br> | | <br> |
| + | == <span style="color:red>I need to establish an authorized access point for a conference, etc., that has been cancelled or held in hybrid mode (both in a physical location and online). Which location should I register in the access point?</span> == |
| | | |
− | ''Last update: 2023-07-18 <!--(2023-07-18)--> | + | <span style="color:red>'''Canceled conferences'''</span> |
| + | </span> |
| + | |
| + | <span style="color:red">If a conference is cancelled, it will likely still yield publications and proceedings and necessitate an AAP. A cancelled conference is understood to have no location, because it did not occur. [http://original.rdatoolkit.org/rdachp11_rda11-4174.html RDA 11.3.2.3] states: “Record a name of place in which the conference, etc., was held …”</span> |
| + | |
| + | <span style="color:red">A cancelled conference will have no location, but could include a number and date. PFAN recommends the following: </span> |
| + | |
| + | <span style="color:red">For numbered conferences: </span> |
| + | *<span style="color:red">Record the number of the meeting in subfield $n</span> |
| + | *<span style="color:red">Record the intended date of the meeting in subfield $d </span> |
| + | *<span style="color:red">Do not record a location</span> |
| + | <span style="color:red">''Example :'' </span> |
| + | <div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;"> |
| + | <span style="color:red">Clinical Nutrition and Research Symposium $n (20e : $d 2020)</span> |
| + | </div> |
| + | |
| + | <span style="color:red">For unnumbered conferences:</span> |
| + | *<span style="color:red">Record the intended date of the meeting in subfield $d</span> |
| + | *<span style="color:red">Do not record a location</span> |
| + | <span style="color:red">''Example :'' |
| + | <div style="font-family:courier new; padding-right:25px; padding-left:100px; padding-top:10px; padding-bottom:10px; line-height:1.4; text-indent:-85px; border:1px solid #eaecf0; background-color:#f8f9fa;"> |
| + | <span style="color:red">SEAALL Annual Meeting $d (2020)</span> |
| + | </div> |
| + | |
| + | <span style="color:red">'''Hybrid conference (in a physical location and online)'''</span> |
| + | |
| + | <span style="color:red">[http://original.rdatoolkit.org/rdachp11_rda11-4174.html RDA 11.3.2.3] does not address the case where a conference is held both in one or more physical |
| + | locations and online. In general, such conferences take place wholly in one or more physical locations with some registrants viewing the proceedings (either in whole or in part) online. </span> |
| + | |
| + | <span style="color:red">In this case, the NACO Advisory Group recommends that the last exception to [http://original.rdatoolkit.org/rdachp11_rda11-4174.html RDA 11.3.2.3] not be applied (i.e. do not record “Online” as a location but instead limit the location to the physical location(s)). |
| + | </span> |
| + | |
| + | ''Last update: 2023-10-26 <!--(2023-10-25)--> |
| [[Category:PFAN]] | | [[Category:PFAN]] |