Consider removing the ISBN(s) from the TEI - Githubissues

SAA-SDT / EAS-TagLibraries

Tag Libraries for Encoded Archival Description Version 3 and Encoded Archival Context: Corporate Bodies, Persons, and Families

7 stars 5 forks source link

Consider removing the ISBN(s) from the TEI #68

Open fordmadox opened 4 years ago

fordmadox commented 4 years ago

Creator of issue

Mark Custer

The issue relates to

[ ] EAC-CPF schema issue
[x] EAC-CPF Tag Library issue
[ ] EAD schema issue
[x] EAD Tag Library issue
[ ] Schema issue
[ ] Tag Library issue
[ ] Suggestions for all schemas
[ ] Suggestions for all Tag Libraries
[ ] Other

Wanted change/feature

Text: We currently include the ISBN for the printed tag library in the TEI (at least for the EAD tag library). See https://github.com/SAA-SDT/EAS-TagLibraries/blob/master/tei/EAD3-TL-eng.xml#L30. Consider removing this from the TEI altogether, or at least removing it from the PDF that is shared online. TS-EAS shouldn't have to worry about ISBNs; those can be handled by SAA at the time of publication for any major revision. Removing this needless level of complexity would more closely align our practice with TS-DACS, and there's really no need that I know of that would require us to manage the ISBN in the TEI and to try to keep that up to date (after one is assigned for printing). Another example, with no ISBN required in the PDF: https://tei-c.org/release/doc/tei-p5-doc/en/Guidelines.pdf

Reporting a bug

Text: Additionally, removing this from the TEI (and the transformation process) would fix the bug we have now with the EAC-CPF PDF tag library, which just includes the label "ISBN Number" with no value.

Suggested Solution

Text: Remove from TEI; update transformation process, if necessary, to not include label; update handbook to make it explicit that TS-EAS doesn't manage ISBNs. We manage the online publications, complete with revision history, but not the creating of print books or e-books that require ISBNs.

Steps to Reproduce (for bugs)

1. 2. 3. 4.

Context

Text:

Your Environment can be a clue to a bug

Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):

alexduryee commented 3 years ago

Done on development (https://github.com/SAA-SDT/EAS-TagLibraries/commit/dea0b88b88029fc8be7914bd6b1defe488ab54a6) - the ISBN is now a command-line argument to the build process.