[DCRM-L] Help with statement of responsibility using DCRM(G)

[Cordes, Ellen]

Erin,

I agree with what you recommend ("$c  [illegible signature]" or "$c John Doe [?]" with explanatory note)  as it is the most accurate reflection of what is on the piece.  There IS a signature, but you cannot read it or speculate what characters (or monogram?) the artist wrote.  Since there is a signature, I agree that you should record the fact in the 245 $c in either way that you suggest, although I prefer the first since if it is a more accurate statement (i.e., not a single letter can be identified).

Ellen

From: dcrm-l-bounces at lib.byu.edu [mailto:dcrm-l-bounces at lib.byu.edu] On Behalf Of Erin Blake
Sent: Saturday, September 13, 2014 11:26 AM
To: DCRM Users' Group
Subject: Re: [DCRM-L] Help with statement of responsibility using DCRM(G)

Actually, DCRM(G) 1G13 is meant to apply whether or not you know who the artist is.

1G2 only applies when there is NO statement of responsibility, or when the statement of responsibility was added after the fact by someone other than the artist (for example, a dealer or curator who helpfully added the name as a sort of label).

DCRM(G) is silent on what to do if the signature is totally illegible AND you know the artist's name. Speaking as chief editor of DCRM(G), I can only say that I guess we assumed that if you knew who the artist was, you'd always be able to make out at least part of the signature. For instance, if you knew the artist was John Doe, but couldn't tell if the signature was "JD" or "J Doe" you could put "J D[oe?]" (following 0G6.2.: Conjectural and indecipherable text).

Can any of the other DCRM editors help me out here? I understand why we don't supply a statement of responsibility when there isn't one, but if there IS one, then omitting the $c is a misrepresentation of the item. Shouldn't we at least indicate in the transcription field that there IS something to transcribe, we just can't figure it out?

Here's what I'd do: because rule 1G3.2 doesn't specifically say NOT to write "$c  [illegible signature]" or "$c John Doe [?]" just that you DO need to record the presence of illegible words in a note, I'd put a conjectural statement of responsibility in the $c and make a note saying that the signature is illegible, but known to be that of John Doe. And maybe later, a scholar who specializes in John Doe's work will recognize what the actual letters are, and you can update the record.

EB.

__________

Erin C. Blake, Ph.D.  |  Head of Collection Information Services  |  Folger Shakespeare Library  | 201 E. Capitol St. SE, Washington, DC 20003  |  office tel. +1 (202) 675-0323  |  fax +1 (202) 675-0328  |  eblake at folger.edu<mailto:eblake at folger.edu>






From: dcrm-l-bounces at lib.byu.edu<mailto:dcrm-l-bounces at lib.byu.edu> [mailto:dcrm-l-bounces at lib.byu.edu] On Behalf Of Sterkenburg, Sara
Sent: Friday, September 12, 2014 11:48 AM
To: DCRM Users' Group
Subject: Re: [DCRM-L] Help with statement of responsibility using DCRM(G)

Hi Marie-Chantal,

Since the artist signed the piece (unless it is completely unrecognizable/illegible), I would definitely bracket in the artist's full name in the 245 $c. In your case, the signature (in my opinion) can be considered a statement of responsibility written in 'manuscript' text, since it's not printed or electronic (see rule below). I would also include a note in your local catalog stating that the piece is signed by the artist.

However, if it is illegible or you would not know who this artist was by the signature alone, then DCRM(G) Section 1G2 directs you to leave it out the 245 $c and put the information in a note field instead:

DCRM(G) Section 1G2:
"If a statement of responsibility is not in text (printed, manuscript, or electronic) provided by the creator or creating body on or with the material, do not supply a bracketed statement. If known, record an attribution and the source of the attribution in a note (see 7B6.3.1). If no attribution can be made, make a note if considered important (see 7B6.3.4)"--Pages 56-57.

Hope that helps!

-Sara

--
Sara Sterkenburg
Cataloging & Exhibition Services Librarian
Vanderbilt University Special Collections Library
(615) 343-1965
sara.sterkenburg at vanderbilt.edu<mailto:sara.sterkenburg at vanderbilt.edu>

From: dcrm-l-bounces at lib.byu.edu<mailto:dcrm-l-bounces at lib.byu.edu> [mailto:dcrm-l-bounces at lib.byu.edu] On Behalf Of L'Écuyer-Coelho Marie-Chantal
Sent: Friday, September 12, 2014 10:27 AM
To: 'dcrm-l at lib.byu.edu'
Subject: [DCRM-L] Help with statement of responsibility using DCRM(G)

Hi,

I need advice from cataloguers experimented with art prints description.
How are we supposed to transcribe the statement of responsibility when the artwork has been signed in pencil by the artist, but the signature is such that we cannot determine if it represents the artist's first name, his/her initials, etc. Since I know the artist's identity, I cannot apply rule 1G13.1 from DCRM(G). Should I simply write a note to mention the work is signed by the artist, without recording anything in 245 $c? Or should I rather the artist's full name in brackets as statement of responsibility?

Many thanks for your help!

Marie-Chantal L'Ecuyer-Coelho
Bibliothécaire
Direction du traitement documentaire des collections patrimoniales
Bibliothèque et Archives nationales du Québec
2275, rue Holt
Montréal (Québec) H2G 3H1
Téléphone : 514-873-1101 poste 3730
mc.coelho at banq.qc.ca<mailto:mc.coelho at banq.qc.ca>
www.banq.qc.ca<http://www.banq.qc.ca/>

Avis de confidentialité Ce courriel est une communication confidentielle et l'information qu'il contient est réservée à l'usage exclusif du destinataire. Si vous n'êtes pas le destinataire visé, vous n'avez aucun droit d'utiliser cette information, de la copier, de la distribuer ou de la diffuser. Si cette communication vous a été transmise par erreur, veuillez la détruire et nous en aviser immédiatement par courriel.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserver.lib.byu.edu/pipermail/dcrm-l/attachments/20140915/308f5f1c/attachment.html>