New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use of msFrag #368
Comments
see also #369 |
i read from the TEI guidelines in the sense that one creates one record for the "abstract" original manuscript as it used to be, which consists then of msFrag each with its own idno/call number. |
like the Codex Suprasliensis example they provide (the Codex only exists as a virtual reconstruction):
|
(Ullendorff's split scroll might fit, if one describes it as one scroll consisting of two msFrag, the rebinding of several fragments of various mss in another codex sounds like a different case) |
I have no objection to the use of msFrag here, although I think the way you have stated this in your file is fine. It might be also a topic worth posting to the TEI list, to see what people have been doing in such cases. |
corrected the ref |
|
Question arrising from BNFet165#p4_i1 (https://archive.org/stream/manuscritsorient00bibl#page/266/mode/2up), which contains several leaves that were detached from BNFet45#ms_i1.1 (https://archive.org/stream/manuscritsorient00bibl#page/42/mode/2up):
I have just stated this information in a note in both mss records, but maybe msFrag should be used here?
Our guidelines state that "msFrag can be used when there are at least two parts of one manuscript kept in different repositories.", but the TEI guidelines state that "The msFrag element may be used inside msDesc when encoding one or more fragments of a scattered or fragmented manuscript. The fragment(s) described in a single msDesc element may be held either at several institutions or at a single institution, so different call numbers may be attached to the fragments. " - this seems to apply to my case.
What do you think?
The text was updated successfully, but these errors were encountered: