Closed zuphilip closed 6 years ago
My only concern with that is that we do want translators to use import translators when possible, not prioritize scrapers. But we could could offer a few different translator types: scraper, RIS import, BibTeX import, etc.
Good point!
But we could could offer a few different translator types
I am not sure how this would be done in the GUI...
Alternatively, we could also provide a link to some (online) documentation about the scrape
function with different template blocks.
I am not sure how this would be done in the GUI...
Can just make the button a menu, with a few translator types under it.
I'd recommend having the default scraper template first pull from EM and have an example of how the scraper can pull the fields missed by the EM translator.
@adam3smith suggested in https://github.com/zotero/translators/issues/1277#issuecomment-286951365
I ignore the FW part but I certainly agree with the remaining. Moreover, we could actually do a new button in Scaffold with the functionality "Add new web translator". This should then create a new id but can also already save a a generic translator template for the start. We can for example start with the lines I have collected and even try something which might run from the beginning (take all
a
nodes in the multiple xpath, set generic title in the scrape). Additional comments can be given for the user to hint where to look for additional code blocks.What do you think? @dstillman