Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Making links to BL_online available in papyri.info #103

Open
jcowey opened this issue Nov 5, 2019 · 2 comments
Open

Making links to BL_online available in papyri.info #103

jcowey opened this issue Nov 5, 2019 · 2 comments
Assignees
@hcayless @Edelweiss @jcowey

Comments

@jcowey
Copy link
Member

jcowey commented Nov 5, 2019

If we decide to encode the link to BL_online, where and how should be encode the information?
Here is a link:

https://aquila.zaw.uni-heidelberg.de/bl/hgv/16679a

For Example HGV id 16679a

The BL corrections you find in HGV file 16679a can also be found on Heidelberg’s online representation of BL. Therefore we wish to make the link to the respective page available within papyri.info, where we would like to see a clickable button or text link next to the bibliography for the BL entries.

So on Papyri.info we would like to see something like…

Post-Concordance BL Entries XII 203 BL online

This information could live inside the EpiDoc file right next to the bibliographical information for BL.

<div type="bibliography" subtype="corrections">
  <head>BL-Einträge nach BL-Konkordanz</head>
  <listBibl>
    <bibl type="BL-online">
      <ptr target="https://aquila.zaw.uni-heidelberg.de/bl/hgv/16679a"/>
    </bibl>
    <bibl type="BL">
      <biblScope type="volume">XII</biblScope>
      <biblScope type="pages">203</biblScope>
    </bibl>
  </listBibl>
</div>

(There are of course many alternative ways for marking up this piece of information. One could, for example, also think of having a separate bibl entry dedicated to online information somewhere outside the listBibl tag, or even another div tag of type »bibliography« but of subtype »corrections-online« <div type="bibliography" subtype="corrections-online">. Ideas and hints to existing formatting of the kind are always welcome.)

If we were using EpiDoc markup as shown above, no changes would have to be made to SoSOL’s HGV metadata editor, but in order to display the data correctly in papyri.info a few changes would be necessary for the EpiDoc stylesheets.

On the one hand, bibl tags of type »BL-online« should be ignored when assembling the content for the metadata field »Post-Concordance BL Entries«. On the other hand, we need to bring the new piece of information to display.

In htm-tpl-metadata.xsl on lines 80-85, the following changes could restrict the displayed data to bibl tags referring to non-online biblbiography and output a link to BL online.

<xsl:for-each select="//t:div[@type = 'bibliography' and @subtype = 'corrections']//t:bibl[@type='BL']">
  <xsl:value-of select="."/>               
  <xsl:if test="not(position() = last())">
    <xsl:text>, </xsl:text>
  </xsl:if>
</xsl:for-each>
 <xsl:if test="//t:div[@type = 'bibliography' and @subtype = 'corrections']//t:bibl[@type='BL-online']/t:ptr/@target">
   <a href="{//t:div[@type = 'bibliography' and @subtype = 'corrections']//t:bibl[@type='BL-online']/t:ptr/@target}" title="BL online" target="_blank" rel="nofollow">BL online</a>
</xsl:if>
@jcowey
Copy link
Member Author

jcowey commented Nov 5, 2019

This simply repeats an issue Carmen made for us: Edelweiss/hgv#93.

@hcayless - would you please have a look at see what you think.

@jcowey
Copy link
Member Author

jcowey commented Nov 14, 2019

In skype call on 13 November it was agreed between Hugh and myself that the above proposed encoding will be fine. Carmen and I can go ahead and get the work done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hcayless hcayless

@Edelweiss Edelweiss

@jcowey jcowey

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hcayless @Edelweiss @jcowey