 |
 |
Thanks, Jason. This is awesome. *Thomas San Filippo* /Systems and Educational Technology Liaison/ Pronouns: he/him/his; they/them/their(s) Madeleine Clark Wallace Library <https://wheatoncollege.edu/academics/library/>, G34 Wheaton College <https://wheatoncollege.edu> 26 E. Main Street, Norton, MA 02766 <https://goo.gl/maps/d5JvoKZUEXy> (508) 286-5601 <tel:+15082865601> Twitter: @WallaceLibrary <https://twitter.com/WallaceLibrary> | Instagram: /wallacelibrary <https://www.instagram.com/wallacelibrary/> | Facebook: wheatoncollege <https://www.facebook.com/WheatonCollege/> On 1/21/20 8:02 AM, Jason Ronallo wrote: > After going through a few iterations for maintaining publications data with > the Citation Index, we've landed on a solution we're generally happy with. > > My recommendation is to not write custom code for citation formats. You'll > be limited to only the formats you write code for and for only the types of > works you consider. You'll start with APA and articles, books, and > chapters, and then realize you need to add IEEE format, consider editors > better, and add conference proceedings and reports. Then what do you do > with persistent identifiers for different formats and also adhere to the > citation formats? So things then quickly get messy and confusing. Others > have already thought through all of this for many more citation formats. > > And then also discard the notion that you'll just use BibTeX. Yes, it is a > structured data format that has been in use a long time. BibTeX might be a > necessary output format. We add BibTeX to ORCID records as the only > structured data which can be added for a work. BibTeX has too many > non-standard flavors, is old to the point that too many types of works get > boiled down to misc, has odd formatting and parsing rules, and software > libraries which have confusing interfaces (even when very well done) > focused on outputting formatted bibliographies. BibTeX is just not enough > to support current needs for managing the necessary data and creating > properly formatted citations. > > Instead consider using CSL-JSON (Citeproc) as your data format: > https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html > > You can then easily output over 1,000 citation styles: > https://github.com/citation-style-language/styles > Lots to recommend CSL including the documentation and maintainers. > > Click the "cite it" links for any publication here to see an example of how > we're able to output in several different formats: > https://ci.lib.ncsu.edu/profiles/kdaniel > > I'll also add that all of this publications data from all sources is messy. > Part of what CSL has allowed us to do is have a common standard to map > other data sources to. The CSL styles then adjust based on whether > particular data is present or not for the type of work given. I could write > a lot more about how our approach has embraced the mess and focused on what > data is necessary to find a work rather than completely filling out > citation formats. > > Jason > > On Tue, Jan 21, 2020 at 5:14 AM Thomas San Filippo < > [log in to unmask]> wrote: > >> Thanks, Deborah. I'd be really interested in seeing that super-messy >> turn-it-to-APA code if you've got it on GitHub or something. >> >> >> *Thomas San Filippo* >> /Systems and Educational Technology Liaison/ >> >> Pronouns: he/him/his; they/them/their(s) >> >> Madeleine Clark Wallace Library >> <https://wheatoncollege.edu/academics/library/>, G34 >> Wheaton College <https://wheatoncollege.edu> >> 26 E. Main Street, Norton, MA 02766 <https://goo.gl/maps/d5JvoKZUEXy> >> (508) 286-5601 <tel:+15082865601> >> Twitter: @WallaceLibrary <https://twitter.com/WallaceLibrary> | >> Instagram: /wallacelibrary <https://www.instagram.com/wallacelibrary/> | >> Facebook: wheatoncollege <https://www.facebook.com/WheatonCollege/> >> On 1/20/20 8:44 PM, Fitchett, Deborah wrote: >>> We use Elements as our research information system. We also had some >> existing staff profile pages (based on Sharepoint). Our ITS was grabbing >> content direct from the Elements database to insert on the profile pages, I >> said “…Have you considered using the API?” and they said “…There’s an API?” >> so long story short I wrote some code that took the staff member’s ID, >> queried the API, and returned a bunch of html listing their research >> outputs in beautiful APA referencing format, which the profile pages ingest >> by, presumably, magic. >>> Over the years it’s sporadically had various minor issues (eg an >> apparently-minor change to the API structure; or a stubborn caching issue >> on the ITS side) and it was often slow especially for the most prolific >> researchers (I only got around to adding caching functionality last year) >> so all in all I’m really glad we’re adding the Discovery module in Elements >> that will do this all properly so I don’t have to maintain the thing. >>> It’s so much fun coding new stuff, it’s just sad that that’s only maybe >> 10% of the total lifetime work… ☺ >>> Anyway, short version: the API side of it was pretty straight-forward >> and even version updates weren’t too much of a hassle to resolve; the >> turning-it-into-APA involved some super messy code but was highly stable; >> the integration into the profiles was probably the hard part but >> fortunately not my problem. >>> Deborah >>> >>> From: Code for Libraries <[log in to unmask]> On Behalf Of Thomas >> San Filippo >>> Sent: Saturday, 18 January 2020 3:10 AM >>> To: [log in to unmask] >>> Subject: Re: [CODE4LIB] API feeding faculty publication profiles >>> >>> We would also be very interested, even if you're not health/medical. >>> >>> Thanks! >>> >>> >>> *Thomas San Filippo* >>> /Systems and Educational Technology Liaison/ >>> >>> Pronouns: he/him/his; they/them/their(s) >>> >>> Madeleine Clark Wallace Library >>> <https://wheatoncollege.edu/academics/library/< >> https://wheatoncollege.edu/academics/library/>>, G34 >>> Wheaton College <https://wheatoncollege.edu<https://wheatoncollege.edu>> >>> 26 E. Main Street, Norton, MA 02766 <https://goo.gl/maps/d5JvoKZUEXy< >> https://goo.gl/maps/d5JvoKZUEXy>> >>> (508) 286-5601 <tel:+15082865601> >>> Twitter: @WallaceLibrary <https://twitter.com/WallaceLibrary< >> https://twitter.com/WallaceLibrary>> | >>> Instagram: /wallacelibrary <https://www.instagram.com/wallacelibrary/< >> https://www.instagram.com/wallacelibrary/>> | >>> Facebook: wheatoncollege <https://www.facebook.com/WheatonCollege/< >> https://www.facebook.com/WheatonCollege/>> >>> On 1/16/20 4:22 PM, Elizabeth Huggins wrote: >>>> Hello, >>>> >>>> My library is looking at platforms for faculty publication profiles. If >>>> you’re working at health sciences or medical library that uses an API to >>>> feed publications into faculty profiles, I would love to hear from you. >>>> Please email me directly at [log in to unmask]<mailto:[log in to unmask]>. >>>> >>>> >>>> Thank you, >>>> >>>> Elizabeth Huggins >>>> >>>> Elizabeth Huggins >>>> MALIS '11 >>>> www.linkedin.com/pub/elizabeth-huggins/43/417/172< >> http://www.linkedin.com/pub/elizabeth-huggins/43/417/172> >>> ________________________________ >>> >>> "The contents of this e-mail (including any attachments) may be >> confidential and/or subject to copyright. Any unauthorised use, >> distribution, or copying of the contents is expressly prohibited. If you >> have received this e-mail in error, please advise the sender by return >> e-mail or telephone and then delete this e-mail together with all >> attachments from your system." >>