Make Alma recognize "Primary Identifier" when creating a set of users
Every time anyone creates an Analytics report on users, if they want it to be usable in Alma via "Create Set," they have to rename the first column of the Analytics report to "Username," which is not a field in the Users subject area in Analytics.
Make the Alma UI accept "Primary Identifier" as a recognized unique identifier so that we can use it to pull User sets from Analytics into Alma.
Definitely makes sense ! We’ll enable the user set to use a column header of “Primary Identifier”.
Tom Kistell commented
This is a really good idea. Thanks for putting it in.
Manu Schwendener commented
It is confusing to have a column identified as something other than the data it represents in troubleshooting a report.
Joe Montibello commented
This is my original message to the list, just for additional context:
"When I create an analytics report on users, I often want to make it a set so I can share it with folks who work on patron records. But it always fails the first time because I always forget to switch the column heading for the first column from "Primary Identifier" to "USERNAME." Then I get into Alma, try to import the set from analytics, and it tells me it doesn't have the right column name:
Header line in input file is missing an ID column. Supported IDs are: FACEBOOK, OTHER_ID_4, OTHER_ID_3, OTHER_ID_2, OTHER_ID_1, BARCODE, USERNAME, UNIV_ID, TWITTER, GOOGLE
Is there any reason why Alma can't be made to recognize that the Primary Identifier field is a valid unique identifier?"