-
Notifications
You must be signed in to change notification settings - Fork 21
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
Stylesheets and transforms for journals and publishers #34
Comments
The quickscrape scrapers are currently in http://github.com/ContentMine/journal-scrapers This may not be quite the right place for them. Probably we should do like we do with dictionaries and have yet another repository for them. Perhaps we should include both the XSLTs and the dictionaries in the repositories that use them (norma and ami) with a git subtree / submodule. I'm currently reading about which is probably a better option for us. |
Good. I think we need to normalize out the publisher stuff and remove specific publishers from |
This currently applies to HTML but may also apply to PDF and TXT transformations.
The HTML translation ( https://github.com/ContentMine/norma/blob/master/docs/TRANSFORM.md ) involves 2 or more stylesheets. Where do we put them and how do we organize it? Should there be a Github repo for publishers, separate from Norma (My current thinking is yes).
Currently we have (for publisher
fooPub
)which contains
toHtml.xsl
, etc.This means we have to rebuild the system for each alteration. If we use stylesheets this can be done independently from
norma
. It would be roughly similar todictionary
.NOTE: we might want to lump together
quickscrape
scrapers andnorma
stylesheets for each journal.The text was updated successfully, but these errors were encountered: