[MEI-L] source-type metadata

[Axel Teich Geertinger]

Hi Benjamin

I think @type on the source element would be a good idea. We are having the same problem, but have solved it for now by using @n instead to categorize the source type, but obviously @type would be more appropriate.
We are using the following values so far:

manuscript_sketch

Manuscript, sketch

manuscript_score_autograph

Manuscript, score, autograph

manuscript_score_copy

Manuscript, score, copy

manuscript_parts_autograph

Manuscript, parts, autograph

manuscript_parts_copy

Manuscript, parts, copy

print_score_first

Printed score, first edition

print_score_later

Printed score, later edition

print_parts

Printed parts

text_ms

Textual source, manuscript

text_print

Textual source, print

other

Other


We then use the source/titlestmt/title element to provide a more specific description of the source, e.g. "Score, fair copy, printer's source" or "Printed part, Ove Scavenius' copy".
If anyone knows a better solution, I'd be happy to know about it.

All the best,
Axel



Fra: mei-l-bounces at lists.uni-paderborn.de [mailto:mei-l-bounces at lists.uni-paderborn.de] På vegne af Benjamin Wolff Bohl
Sendt: 15. september 2010 11:25
Til: mei-l at lists.uni-paderborn.de
Emne: [MEI-L] source-type metadata

Hi Mei-List(eners)!

I got a question concerning the location of some metadata I would like to put into an MEI-file.
I just don't know where I should put it.

I would like to store a type on a source element I have, specifying whether it is a print or an autograph, maybe even more like a copyists copy or an edition.

So in my code I have the following:

<sourcedesc>
                <source xml:id="source_3c94e494-bc7e-4233-a27d-17671fc8d933">
                    <titlestmt>
                        <title>Londoner Abschrift</title>
                    </titlestmt>
                   <pubstmt>
                        <date reg="2010">2010</date>
                       <identifier type="siglum">K2</identifier>
                    </pubstmt>

Now I wondering whether the right place of such data would be an editionstmt or maybe the physdesc, which could contain even more detailed data concerning the creation of the source? (see below)

                    <physdesc>
                        <physmedium n="type">
                        <physmedium n="support"></physmedium>
                        <physmedium n="content"></physmedium>
                        <physloc/>
                    </physdesc>
                </source>
            </sourcedesc>

O would it be best/easiest to have @type on source? (which currently is not possible)

Cheers,

Benjamin

***********************************************************
Projekt "Digitale Musikedition"
Musikwissenschaftliches Seminar Detmold/Paderborn
Gartenstraße 20
D - 32756 Detmold

Tel. +49 (0) 5231 / 975-665
Fax: +49 (0) 5231 / 975-668
***********************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20100915/4b6acc40/attachment.htm>