Hi,
I reached out to a variety of folks, including one of the FOLIO developers (who happens to be a buddy of mine) and he had a good answer:
Phil
“
=======
I'm not sure if this will be helpful but the pre-populated user records in our folio-snapshot and folio-testing envs have the "type" field currently set to "patron" (please
see the attached image). That field is not being used by the UI anywhere.
We had some conversations in the past about different types of users. One of them being "system" which could be potentially used to perform some background actions etc.
Cheers,
Michal
“
Philip Robinson
Director of Library Systems
Cornell University
(607) 255-0098
From: <user-mgmt@ole-lists.openlibraryfoundation.org> on behalf of Tania Hewes Fersenheim <tahewes@gmail.com>
Reply-To: "user-mgmt@ole-lists.openlibraryfoundation.org" <user-mgmt@ole-lists.openlibraryfoundation.org>
Date: Wednesday, March 13, 2019 at 10:43 AM
To: "user-mgmt@ole-lists.openlibraryfoundation.org" <user-mgmt@ole-lists.openlibraryfoundation.org>
Subject: Re: Agenda items for tomorrow's meeting
Hi all,
A potential partial answer for the user.json.type question.
Poking around on the wiki I found a doc that seems to attempt to map Voyager, Aleph, etc user data elements into userdata.json and userdataimport.json which may or may not be useful to a discussion of user.json
type is described (for userdataimport.json) as "class of user", analogous to Voyager patron_name_type.patron_name_desc and to Aleph z305_bor_status
I'm hoping we hear back from someone on the slack channel
Tania
On Tue, Mar 12, 2019 at 4:58 PM Maura Byrne <byrne@uchicago.edu> wrote: