Closed tacarlson closed 11 years ago
This approach has been changed to adding a citedRange element with attributes of unit=entry and target containing the url.
initial demo milestone or defer?
I would put this in the initial demo, to show even our first users that there will be bibliographic information from CBSC where available (and to build good will with Sergey), even though the precise state of that info will change. But it's @davidamichelson 's call.
@paregorios We need a live link to CBSC in the demo either in the citation or in the see also section please. This will help in making the case to our biblio partners as Thomas notes and will give a fake taste of linked open data to our users since CBSC is a source they already use.
In the new data which I just committed, within the <bibl> entries pointing to the Comprehensive Bibliography on Syriac Christianity (CBSC) I have added a <title> with @level="a" whose content is the names of the CBSC entry or entries for this place (within quotes, comma-separated). Within the <bibl> I also added <ref> element(s) whose @target attribute(s) point(s) to the CBSC entry URLs (which are not URIs, and have nasty ampersands and spaces, so ampersands are encoded with &).
It would be great if we could surface the article titles and make each article title a link to the CBSC entry corresponding to it. Each CBSC link should contain the article title exactly, and I do not believe there are any truncation collisions (e.g. where one of the names of this place is a proper substring of another). So if you iterate through the article titles (stripping out quotation marks and comma) you can search which <ref> has a @target which contains that string.
This is of course a temporary enhancement until we merge with CBSC, but Dave thought it would be worthwhile to enable this and then tweak it later.