We did a short write-up of the thoughts behind our little name app at 
Open Repositories last year.

Here is a link to the paper.

We currently create new name records for people when they get added 
to the UNT Scholarly Works Repository.  We aren't creating records for 
all possible authors,  just authors that we come into contact with from
submitted items.

As we add a new author we try to link them to VIAF, LoC, ResearchGate,
our local faculty profile system and a few other places.

Right now we are still storing the authorized name format in the records
and not the identifier but that is something we are working through so that
we can store the identifiers and not just the name strings. 

Each name record has an added link which sends you into the digital 
collections to view items with that name in the metadata.

I've had a number of people ask about the code for this and we will work
to get it added to our github repository.  It is a very simple Django app. 

And a final random note,  we are also starting to create records for buildings 
on our campus as we digitize more of our university archives.  Here is a record
for our research park building.


From: Code for Libraries [[log in to unmask]] on behalf of Tim Thompson [[log in to unmask]]
Sent: Thursday, June 05, 2014 9:13 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] orcid and researcherid and scopus, oh my

Something like the UNT Name App strikes me as right in line with the
BIBFRAME Authorities model and its "lightweight abstraction layer" ( Imagine if every
research institution started maintaining a local authority file like this
and exposed it as RDF: the LOD-LAM linked data cloud could start to scale
up very quickly.

Mark, how is the UNT Name App being populated/maintained? Are there plans
to link these local identifiers to objects in the digital collections? Is
the source code available?

As for aggregating/cross-walking identifiers in general, I think Wikidata ( holds a lot of potential (see, for example, the
Wikidata item for Barack Obama:


Tim A. Thompson
Metadata Librarian (Spanish/Portuguese Specialty)
Princeton University Library
693 Alexander Road, 2nd Floor
Princeton, New Jersey 08540

(609) 258-2597 (office)
(201) 423-9972 (mobile)
[log in to unmask]

On Wed, Jun 4, 2014 at 2:52 PM, Phillips, Mark <[log in to unmask]>

> We are including these identifiers in the authority records we create for
> our system.
> Here is an example record in the UNT Name App for me with some of these
> links.
> Here is a record with VIAF and LC identifiers integrated.
> Right now we are just storing these links and how they relate to our local
> identifiers for a person, organization, event, or building in our name app.
> Don't know if that is helpful or not.
> Mark
> ________________________________________
> From: Code for Libraries [[log in to unmask]] on behalf of Eric
> Lease Morgan [[log in to unmask]]
> Sent: Wednesday, June 04, 2014 1:34 PM
> To: [log in to unmask]
> Subject: [CODE4LIB] orcid and researcherid and scopus, oh my
> ORDID and ResearcherID and Scopus, oh my!
> It is just me, or are there an increasing number of unique identifiers
> popping up in Library Land? A person can now be identified with any one of
> a number of URIs such as:
>   * ORCID -
>   * ResearcherID -
>   * Scopus -
>   * VIAF -
>   * LC -
>   * ISNI -
> At least these identifiers are (for the most part) “cool”.
> I have a new-to-me hammer, and these identifiers can play a nice role in
> linked data. For example:
>   @prefix dc: <> .
>   <> dc:creator
>     "" ,
>     "" ,
>     "" ,
>     "" .
> How have any of y’all used theses sorts of identifiers, and what problems
> do you think you will be able to solve by doing so? For example, I know of
> a couple of instances where these sort of identifiers are being put into
> MARC records.
> —
> Eric Morgan