Skip to content

NAV3

Jump to bottom
Pietro Liuzzo edited this page Mar 28, 2018 · 20 revisions

Catalogue Record View

Description

The preview structure constitutes a stub, of the order and structure of the description.

for distinct msParts it would be better to structure the description in Codicological units and not repeat "of p1" etc. (see here http://www.e-codices.unifr.ch/en/description/ubb/F-III-0025/HAN or also http://www.e-codices.unifr.ch/en/description/fcc/0060/)

Notes

we need to work on an example to render the stratigraphy of a manuscript based on the description.

The description should be done in history within the msDesc, msPart or msFrag as appropriate and make proper use of provenance acquisition and origin whereas the information available which does not belong there could be provided in summary. This should be then visualized as a stratigraphy based on dates e.g.

each of these could have a simple @n and/or @xml:id identifying the stratigraphic sequence when possible this could be visualized using the numbering of the strata in a schematic way, e.g. as follows.

str. 1 (date) str. 2 str. 3 str. 4 str. 5 (date)
p1.1 was written by h2 h3 added a5
p.1.2 was written by h1 h5 added a2 and deleted i2 to replace it with a3
p.2 was written by h3 h4 corrected p.2 with interlinear notes

at COMSt conference Andrist has presented this StruViMan tool which could do something similar and will be open access. more info needed!

distinguish production and circulation units in visualization. this needs to be coded in the history pointing to the described items. grouping the units. needs explicit description of the UniCirc?

<uniCirc n="1" corresp="p1.1">
<uniProd n="1" corresp="p1.1.">
</uniProd>
</uniCirc>

would it work? needs to be defined as TEI extension for Synthax du codex encoding?

Implementation

USING XSLT in EXIST

test reuse of preview did not work fully

fall backs of filelook up do not work. probably due to externalization of process (see p. 240 of exist manual). needs rewriting in XQuery

diacritics in edition

  • Red color – to indicate red inks hi[@rend='rubric']
  • /letter/-to indicate later correction add[@hand, @place]
  • {Letter or just space} – to indicate that the top layer of the parchment was removed and the text was written again. This kind of correction is not visible from the photo, but clear on the parchment. subst/del[@rend'erasure']
  • bla[bla ] bla – to indicate, that the text is marked with marginal sign
  • Ludolfus 12 – first hand
  • Ludolfus 14 fat – second hand
  • Ludolfus 10 – fifth hand
  • Green color – to indicate correction made probably with very thin pen, third hand
  • Line below –line above that means “deleted”
  • reddish color - fourth hand
  • pinkish color- sixth hand
  • greenish color- seventh hand
      • to indicate a sign, pointing the place where the text should be added <gap reason="illegible" unit="chars" quantity="1"/>
  • _ - just as a sign – to imitate the sign made by the copyist g
  • ? – when I am not sure how to interpret unclear
  • = ???

Prerequisites

Synthax du Codex ontology

example 1 BDLaethe8

(issue 327)[#327] could be represented like this

<listRelation>
         <relation active="BDLaethe8#p3" name="SdC:constituteUnit" passive="BDLaethe8#UniCirc1"/>
         <relation active="BDLaethe8#p3" name="SdC:undergoesTransformation" passive="BDLaethe8#tr1"/>
         <relation active="BDLaethe8#p1" name="SdC:undergoesTransformation" passive="BDLaethe8#tr1"/>
         <relation active="BDLaethe8#p2" name="SdC:undergoesTransformation" passive="BDLaethe8#tr1"/>
         <relation active="BDLaethe8#tr1" name="SdC:hasTransformationModel" passive="SdC:A1"/>
         <relation active="BDLaethe8#tr1" name="SdC:produces" passive="BDLaethe8#UniCirc2"/>
         <relation active="BDLaethe8#UniCirc2" name="skos:exactMatch" passive="BDLaethe8"/>
         
      </listRelation>

which produces the following graph

 <rdf:Description rdf:about="http://betamasaheft.eu/BDLaethe8/mspart/p3">
      <SdC:constituteUnit rdf:resource="http://betamasaheft.eu/BDLaethe8/UniCirc/UniCirc1"/>
   </rdf:Description>
   <rdf:Description rdf:about="http://betamasaheft.eu/BDLaethe8/UniCirc/UniCirc1">
      <rdf:type rdf:resource="http://Synthax.du.Codex/ontology#UniCirc"/>
      <SdC:undergoesTransformation rdf:resource="http://betamasaheft.eu/BDLaethe8/transformation/tr1"/>
   </rdf:Description>
   <rdf:Description rdf:about="http://betamasaheft.eu/BDLaethe8/mspart/p1">
      <SdC:undergoesTransformation rdf:resource="http://betamasaheft.eu/BDLaethe8/transformation/tr1"/>
   </rdf:Description>
   <rdf:Description rdf:about="http://betamasaheft.eu/BDLaethe8/mspart/p2">
      <SdC:undergoesTransformation rdf:resource="http://betamasaheft.eu/BDLaethe8/transformation/tr1"/>
   </rdf:Description>
   <rdf:Description rdf:about="http://betamasaheft.eu/BDLaethe8/transformation/tr1">
      <rdf:type rdf:resource="http://Synthax.du.Codex/ontology#Transformation"/>
      <SdC:hasTransformationModel rdf:resource="http://Synthax.du.Codex/ontology#A1"/>
   </rdf:Description>
   <rdf:Description rdf:about="http://betamasaheft.eu/BDLaethe8/transformation/tr1">
      <rdf:type rdf:resource="http://Synthax.du.Codex/ontology#Transformation"/>
      <SdC:produces rdf:resource="http://betamasaheft.eu/BDLaethe8/UniCirc/UniCirc2"/>
   </rdf:Description>
   <rdf:Description rdf:about="http://betamasaheft.eu/BDLaethe8/UniCirc/UniCirc2">
      <rdf:type rdf:resource="http://Synthax.du.Codex/ontology#UniCirc"/>
      <skos:exactMatch rdf:resource="http://betamasaheft.eu/BDLaethe8"/>
   </rdf:Description>

which says that the three parts, but only to the part 3 is assigned also the status of Circulation Unit. Each part is by default in the UniProd class. all three parts have undergone a transformation which gets an id, this annotation is added to a class in the ontology and is said to produces a new Circulation unit, which also gets a new id and is declared to be what we have now by equating it to the current ms.

the class assignment are derivated by the ids processed by the data2rdf.xslt transformation

This is now correctly serialized as jsonld for d3.js usage and has been integrated in the analytic view, although labels do not yet work

Example 2 BDLaethf11 and BDLaethf12

The case of BDLaethf11 and BDLaethf12 is also one where we should use this kind of relational encoding. also, both of them should be encoded with msPart, as they are not reconstructed manuscript at any stage, they represent the current Circulation Units.

In this case some repetition is not necessary but I think useful, because the user could start from either of the entities.

in BDLaethf11 one could add

<listRelation>
            <relation active="BDLaethf11#UniCirc1" name="SdC:undergoesTransformation" passive="BDLaethf11#tr1"/>
            <relation active="BDLaethf11#UniCirc1" name="dcterms:hasPart" passive="BDLaethf11#p1 BDLaethf11#p2 BDLaethf12"/>
            <relation active="BDLaethf11#tr1" name="SdC:hasTransformationModel" passive="SdC:D3"/>
            <relation active="BDLaethf11#tr1" name="SdC:produces" passive="BDLaethf11#UniCirc2 BDLaethf11#UniCirc3"/>
            <relation active="BDLaethf11#UniCirc2" name="skos:exactMatch" passive="BDLaethf11"/>
            <relation active="BDLaethf11#UniCirc3" name="skos:exactMatch" passive="BDLaethf12"/>
         </listRelation>

and in BDLaethf12 one could add

<listRelation>
            <relation active="BDLaethf12#UniCirc1" name="SdC:undergoesTransformation" passive="BDLaethf12#tr1"/>
            <relation active="BDLaethf11#UniCirc1" name="skos:exactMatch" passive="BDLaethf12#UniCirc1"/>
            <relation active="BDLaethf12#tr1" name="skos:exactMatch" passive="BDLaethf11#tr1"/>
            <relation active="BDLaethf12#tr1" name="SdC:hasTransformationModel" passive="SdC:D3"/>
            <relation active="BDLaethf12#UniCirc1" name="dcterms:hasPart" passive="BDLaethf11#p1 BDLaethf11#p2 BDLaethf12"/>
            <relation active="BDLaethf12#tr1" name="SdC:produces" passive="BDLaethf12#UniCirc2 BDLaethf12#UniCirc3"/>
            <relation active="BDLaethf12#UniCirc2" name="skos:exactMatch" passive="BDLaethf11"/>
            <relation active="BDLaethf13#UniCirc3" name="skos:exactMatch" passive="BDLaethf12"/>
         </listRelation>

in the second there are a couple more equations to entities declared in the previous, but this also allows to analyze one only

Example 3 BNFet45 and BNFet165

BNF et 45 and BNF et 165, which contains leaves detached from BNF et 45.

BNF et 45 is not a reconstructed manuscript, is there, just it does not have any more those leaves, which constitute a fragment of it.

This situation is described in La Synthax du codex as MA1. it will be encoded relationally with properties and classes from the ontology.

Note that I assume in this example that BNF et 45 has a msPart with id p1 and a msFrag with id f2

ideally we will have in BNFet45

<listRelation>
            <relation active="BNFet45#UniCirc1" name="dcterms:hasPart" passive="BNFet45#p1 BNFet45#f2"/>
            <relation active="BNFet45#UniCirc1" name="SdC:undergoesTransformation" passive="BNFet45#tr1"/>
            <relation active="BNFet45#tr1" name="SdC:hasTransformationModel" passive="SdC:D2"/>
            <relation active="BNFet45#tr1" name="SdC:produces" passive="BNFet45#UniCirc2"/>
            <relation active="BNFet45#tr1" name="SdC:produces" passive="BNFet45#UniProd1"/>
            <relation active="BNFet45#tr1" name="SdC:isPartOfTransformation" passive="BNFet45#tr3"/>
            <relation active="BNFet45#UniCirc2" name="dcterms:hasPart" passive="BNFet45#p1"/>
            <relation active="BNFet45#UniCirc2" name="skos:exactMatch" passive="BNFet45"/>
            <relation active="BNFet45#UniProd1" name="dcterms:hasPart" passive="BNFet45#f2"/>
            <relation active="BNFet45#UniProd1" name="SdC:undergoesTransformation" passive="BNFet45#tr2"/>
            <relation active="BNFet45#tr2" name="SdC:hasTransformationModel" passive="SdC:A4"/>
            <relation active="BNFet45#tr2" name="skos:exactMatch" passive="BNFet165#tr1"/>
            <relation active="BNFet45#tr2" name="SdC:isPartOfTransformation" passive="BNFet45#tr3"/>
            <relation active="BNFet45#tr3" name="SdC:hasTransformationModel" passive="SdC:MA1"/>
         </listRelation>

and in BNF et 165

<listRelation>
           <relation active="BNFet165#UniCirc1" name="dcterms:hasPart" passive="BNFet165#p1 BNFet165#p2 BNFet165#p3 BNFet165#p5 BNFet165#p6"/>
           <relation active="BNFet165#UniCirc1" name="SdC:undergoesTransformation" passive="BNFet165#tr1"/>
           <relation active="BNFet165#tr1" name="SdC:hasTransformationModel" passive="SdC:A4"/>
           <relation active="BNFet165#tr1" name="SdC:isPartOfTransformation" passive="BNFet45#tr3"/>
           <relation active="BNFet165#tr1" name="skos:exactMatch" passive="BNFet45#tr2"/>
           <relation active="BNFet165#tr1" name="SdC:produces" passive="BNFet165#UniCirc2"/>
           <relation active="BNFet165#UniCirc2" name="dcterms:hasPart" passive="BNFet165#p1 BNFet165#p2 BNFet165#p3 BNFet165#p4 BNFet165#p5 BNFet165#p6"/>
           <relation active="BNFet165#UniCirc2" name="skos:exactMatch" passive="BNFet165"/>           
           <relation active="BNFet165#p4" name="skos:exactMatch" passive="BNFet45#f2"/>
        </listRelation>

Example 4 BNFet45 and BNFet165

In BAVcerulli37 a unit has probably been added

<relation active="BAVcerulli37#p1" name="SdC:constituteUnit" passive="BAVcerulli37#UniProd1"/>
                <relation active="BAVcerulli37#p2" name="SdC:constituteUnit" passive="BAVcerulli37#UniProd2"/>
                <relation active="BAVcerulli37#UniProd2" name="SdC:hasCertainty" passive="SdC:Hypothetique"/>
                <relation active="BAVcerulli37#UniProd1" name="SdC:undergoesTransformation" passive="BAVcerulli37#tr1"/>
                <relation active="BAVcerulli37#UniProd2" name="SdC:undergoesTransformation" passive="BAVcerulli37#tr1"/>
                <relation active="BAVcerulli37#tr1" name="SdC:hasTransformationModel" passive="SdC:A1"/>
                <relation active="BAVcerulli37#tr1" name="SdC:produces" passive="BAVcerulli37#UniCirc2"/>
                <relation active="BAVcerulli37" name="skos:exactMatch" passive="BAVcerulli37#UniCirc2"/>
                <relation active="BAVcerulli37#UniProd1" name="SdC:constituteUnit" passive="BAVcerulli37#UniCirc1"/>
                <relation active="BAVcerulli37#UniCirc1" name="dcterms:hasPart" passive="BAVcerulli37#p1"/>
                <relation active="BAVcerulli37#UniCirc2" name="dcterms:hasPart" passive="BAVcerulli37#p1 BAVcerulli37#p2"/>

back to list

To create new requirements please use this template. For a new use case please use this template

Guidelines

Upgrades and Releases

Clone this wiki locally