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.
Seems to actually have been working already, see https://www.screencast.com/t/FFTvmubE
-
Joe Montibello commented
For me, the problem doesn't happen when I'm pulling a report from Analytics directly into Alma. However, because that process has been so slow lately, I have started exporting from Analytics to a file and then uploading the file because it's faster.
When I upload a User file from Analytics with the "Primary Identifier" field as the first column, I get a non-specific error message ("Oops, there was a problem performing the last action"), and the set doesn't get created. Then I change the column header to "username," and it successfully creates the set.
Exporting from Analytics: https://www.screencast.com/t/71OFkbnlyIO8
Importing file into Alma Sets: https://www.screencast.com/t/oEt3jeInL
Error message: https://www.screencast.com/t/eBQAiZ3MjTL
Change column header: https://www.screencast.com/t/71OFkbnlyIO8
Success: https://www.screencast.com/t/e4tlj0iZ -
Joe Montibello commented
This problem seems to have recurred, at least for me:
https://dartgo.org/primaryidnotworking
I have no idea what might have changed.
-
Joe Montibello commented
Whoops, I can't delete it, so everyone will have to just take their votes away from this idea (and put them toward something else!)
-
Joe Montibello commented
I don't know when this got fixed but it does seem like it's working for me, I just tried it and it's now accepting the Primary Identifier field. I'll delete this idea so the votes go back to everyone who voted. Thanks!
Joe M.
-
Tom Kistell commented
This is a really good idea. Thanks for putting it in.
-
Manu Schwendener commented
+1
-
KF 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?"