For external users - Designate field such as statistical category type and user note to be internal data segments

[stephroach]

Hi--When enriching an external user with the app, we'd like a way to identify a specific fields such as "Statistical Category Type" and "User note" to be internal data. This way we can add the statistical category type and user note as internal data segments and it won't get written over when the SIS load occurs later. Thanks.

[kolarikj]

Is there any chance this will get done? The only workaround seems to be to reload all the records after every SIS update.

[mgobat]

@stephroach, would the use case be to add/update both internal and external segments to external users using one run of the Cloud App, or would you not mix internal and external segment add/update in the same CSV file?

[kolarikj]

The use case: Currently, our FTP load overwrites the CSV data we've tried loading daily. We do not load statistics via FTP. No user_statistics stanza appears in the FTPd XML. We have tried loading user statistics via CSV. Everything is overwritten by the FTP load. According to the documentation, if the user statistics fields were internal they would not be overwritten. Since external field get overwritten, we have no use case for loading external. I've been meaning to try adding an internal field via API but haven't had time yet -- just to check that it isn't also overwritten Thank you for asking Joan = = = = = = Joan Kolarik Manager, Library Integrated Technology Systems W. W. Hagerty Library Drexel University +1-215-895-1344 library.drexel.edu<https://www.library.drexel.edu/>

…

________________________________ From: mgobat ***@***.***> Sent: Thursday, February 22, 2024 8:32:41 AM To: ExLibrisGroup/alma-csv-user-load ***@***.***> Cc: kolarikj ***@***.***>; Comment ***@***.***> Subject: Re: [ExLibrisGroup/alma-csv-user-load] For external users - Designate field such as statistical category type and user note to be internal data segments (Issue #97) @stephroach<https://github.com/stephroach>, would the use case be to add/update both internal and external segments to external users using one run of the Cloud App, or would you not mix internal and external segment add/update in the same CSV file? — Reply to this email directly, view it on GitHub<#97 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACLOSQJIXVVZZQO5CJP2BALYU5CHTAVCNFSM6AAAAAA3RT22O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZGQ3DCNZVGI>. You are receiving this because you commented.Message ID: ***@***.***>

[stephroach]

@mgobat , we have two use cases for updating / creating external users. One only adds internal data segments, the other adds both internal and external data segments.

When updating existing external users, we have only needed to add internal data segments (notes, statistical category type) since we rely on the SIS load to update the external data segments.

When creating new external users (set to SIS_TEMP), we would need to load both internal and external data segments (things like Primary ID, names, contact info, etc. get set to external, and then notes and statistical category type are set to internal).

When creating new external (SIS_TEMP) users from the .csv file, we could use one .csv load for internal segments and a separate .csv load for external segments if needed. However it would be nice to do it in one .csv file load if possible, and if the user interface of the Cloud App didn't become to clunky to manage both internal and external data segments for external users.

[mgobat]

@kolarikj, @stephroach Thank you for the additional information.

@kolarikj, I think you'll get the same results using the API as the Cloud App.

@stephroach, we have the same concern about keeping the UI and CSV file manageable if trying to update both internal and external segments in the same run of the Cloud App.

This enhancement reaches beyond the Cloud App and into the Alma APIs used by the Cloud App. Therefore, this enhancement, if done, will be tied to a particular Alma release.