Two other projects that are worth taking a look at are VIVO [1] and BibApp [2]. Both take the approach of enabling institutions to manage information about their faculty, which can then be federated more widely. I guess the reality is that there will be lots of identifiers for faculty, and simple systems that allow them to be collaboratively and meaningfully linked together are a good way forward.
//Ed [1] http://vivoweb.org/ [2] http://bibapp.org/ On Fri, Apr 13, 2012 at 1:03 PM, Paul Butler (pbutler3) <pbutl...@umw.edu> wrote: > Thank you all for your suggestions! Kevin's excellent email confirms my > suspicions. > > I am working on plans to transform our digital repository to a more broadly > defined IR, so that will likely be our focus down the road. However, any > solution that requires faculty input without an immediate, tangle benefit > will likely gain slow traction. > > I will pass along the suggestions and go from there. > > Cheers, Paul > +-+-+-+-+-+-+-+-+-+-+-+-+ > Paul R Butler > Assistant Systems Librarian > Simpson Library > University of Mary Washington > 1801 College Avenue > Fredericksburg, VA 22401 > 540.654.1756 > libraries.umw.edu > > Sent from the mighty Dell Vostro 230. > > > -----Original Message----- > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Ford, > Kevin > Sent: Friday, April 13, 2012 10:50 AM > To: CODE4LIB@LISTSERV.ND.EDU > Subject: Re: [CODE4LIB] Author authority records to create publication feed? > > Hi Paul, > > I can't really offer any suggestions but to say that this is a problem area > presently. In fact, there was a recent workshop, held in connection with the > Spring CNI Membership Meeting, designed specifically to look at this problem > (and author identity management more generally). You can read more about it > from the announcement here [1], but the idea was to bring a number of the > larger actors (Web of Science, arXiv, ORCID, ISNI, VIAF, LC/NACO, and a few > more) involved in managing authorial identity together to learn about the > work being done, and to discuss improved ways, to disambiguate scholarly > identities and then diffuse and share that information within and across the > library and scholarly publishing realms. Clifford Lynch, who moderated the > meeting, will publish a post-workshop report in a few weeks [2]. Perhaps of > additional interest, [2] also contains a link to the report of a similar > workshop held in London about international author identity. > > Inititatives like ISNI [3] and ORCID [4], which mint identifiers for (public, > authorial) identities, and VIAF, which has done so much to aggregate the > authority records of the participating libraries (while also assigning them > an identifier), are essential to disambiguating one identity from another and > assigning unique identifiers to those identities. For identifiers like > ORCIDs, the faculty member's sponsoring organization might acquire the ORCID > for him/her, after which the faculty member will/may know and use the > identifier in situations such as grant applications, publishing, etc. (though > it might also be early days for this activity also). Part of the process, > however, is diffusing the identifier across the library and scholarly > publishing domains, all the while matching it with the correct identity (and > identifer) in another system. That said, when ISNIs and ORCIDs and, perhaps, > VIAF identifiers start to make their ways into Web of Science, arXiv, LC/NACO > file, ! an! > > d many other places, we - developers looking to creating RSS feeds of author > publications across services but without having to deal with same-name > problems or variants - might then have the hook we need to generate RSS feeds > for author publications from such services as JSTOR, EBSCO, arXiv, Web Of > Science, etc. > > Alternatively, you'd have to get your faculty members to submit their entire > publication history to academia.edu (as Ethan suggested), after which the > community would have to request an RSS feed of that history, or an > institutional repository (as Chad suggested), but I understand these types of > things are an uphill battle with (often busy, underpaid) faculty. > > Cordially, > > Kevin > > > [1] http://www.cni.org/news/cni-workshop-scholarly-id/ > [2] https://mail2.cni.org/Lists/CNI-ANNOUNCE/Message/113744.html > [3] http://www.isni.org/ > [4] http://about.orcid.org/ > > > > > > >> -----Original Message----- >> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf >> Of Paul Butler (pbutler3) >> Sent: Friday, April 13, 2012 9:25 AM >> To: CODE4LIB@LISTSERV.ND.EDU >> Subject: [CODE4LIB] Author authority records to create publication feed? >> >> Howdy All, >> >> Some folks from across campus just came to my door with this question. >> I am still trying to work through the possibilities and problems, but >> thought others might have encountered something similar. >> >> They are looking for a way to create a feed (RSS, or anything else >> that might work) for each faculty member on campus to collect and link >> to their publications, which can then be embedded into their faculty >> profile webpage (in WordPress). >> >> I realize the vendors (JSTOR, EBSCO, etc.) allow author RSS feeds, but >> that really does not allow for disambiguation between folks with the >> same name and variants in name citation. It appears Web of Science >> has author authority records and a set of apis, but we currently do >> not subscribe to WoS and am waiting for a trial to test. What we need >> is something similar to this: http://arxiv.org/help/author_identifiers >> >> We can ask faculty members to upload their own citations and then just >> auto link out to something like Serials Solutions' Journal Finder, >> but that is likely not sustainable. >> >> So, any suggestions - particularly free or low cost solutions. Thanks! >> >> Cheers, Paul >> +-+-+-+-+-+-+-+-+-+-+-+-+ >> Paul R Butler >> Assistant Systems Librarian >> Simpson Library >> University of Mary Washington >> 1801 College Avenue >> Fredericksburg, VA 22401 >> 540.654.1756 >> libraries.umw.edu >> >> Sent from the mighty Dell Vostro 230.
