-
Notifications
You must be signed in to change notification settings - Fork 3
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
Consider providing a Highwire Press Tags mapping for SRAP #67
Comments
Thanks for the suggestion @nishad ! We will take a look. |
There are quite a few vocabularies that we might want to address. We did a spreadsheet with some of these although that was in an attempt to identify vocabularies we could use. We did do a comparison to RIOXX which seemed to be operating in the same space. Because there are many vocabularies for academic publications as well as for unpublished materials, we probably need a general approach to locating SRAP within the academic resource description environment. That may be a lot of work but there should probably be a statement as to why yet another vocabulary is needed. Here's what Zotero can export: ![]() |
@kcoyle, thank you for clarifying and for the details on Zotero's various export formats. While interesting, it is unrelated to my original request. For clarity, Highwire Press Tags are not export formats or a proper semanticweb vocabulary but rather metadata tags that publishers use in their online publications fronts of the repositories. These tags are used by tools 'like' Zotero, other scholarly/acadamic browser extensions, and indexing services like Google Scholar to automatically extract metadata from scholarly content on the web. Perhaps if you're interested in understanding what Highwire Press Tags actually are, the Zotero documentation on exposing metadata would clarify why this is fundamentally different from export formats. My suggestion was simply to help SRAP implementers map their metadata to this widely adopted industry practice that most citation tools and academic search engines rely on. This is strictly an implementation concern for publishers adopting SRAP who want their content to remain discoverable; it is not very relevant for other use cases of SRAP. That said, I completely understand this may be outside the current scope of this work. As I mentioned, this is primarily relevant to web publishers implementing SRAP, who can certainly work with metadata experts to develop these mappings themselves. As mentioned in my original post, this is a niche concern that primarily affects web publishers. Please feel free to close this issue if you believe it falls outside the project's scope. Thank you for your consideration. |
Description
Highwire Press Tags continue to be utilized by many scholarly indexing services (including in the Google Scholar indexing requirements) and reference management tools like Zotero. While SRAP is already well-documented, some implementers might benefit from having a mapping between Highwire Press Tags and SRAP.
Background
This suggestion comes from observing that smaller publishers and implementers sometimes face challenges when transitioning between different metadata schemas. A mapping document could assist those with limited resources to more easily implement SRAP alongside existing systems.
Possible Approach
If the team feels this would be valuable, perhaps consider:
Potential Benefits
Resources
Existing mapping examples, such as this guide by D. I. Verrelli, could serve as references.
Priority
This is merely a suggestion that might enhance usability for some potential SRAP adopters, and I completely understand if it falls outside current priorities or scope.
The text was updated successfully, but these errors were encountered: