Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

DescriptionResolutionStatusExpected Resolution Date
User Rejected: missing a mandatory field: statistical category

The PS code assumes everyone should have a Dept/Major, but retirees and visiting scholars don't, so it creates a statistical category but doesn't supply a value, which Alma (rightly) complains is illegal. So the fix is just to not include that category at all for those user types.

It's scheduled for the next PS release (MP 25) in early June. I hope everyone is okay to wait for that.

PENDING

early June

Invalid byte 1 of 1-byte UTF-8 sequence

PS Code outputs the file non-explicitly as UTF-8 encoding. Should be a CMS fix, to set UTF-8 as charset when opening the file for writing. In the meantime, can fix individual records with potential UTF-8 encoding problems.

PENDING


Identifier of type OTHER_ID_2 and value <some_value> is already taken AcrossInstitution.

Caused by duplicate Alma records. Resolution: delete one of the records in Alma.

KNOWN FIX


Mandatory field is missing: User identifier value

Missing identifier. Resolution: Fix in PeopleSoft. User identifier segment might look something like this:

<user_identifiers>
<user_identifier segment_type="External">
<id_type desc="Additional ID 2">OTHER_ID_2</id_type>
<value></value> <----note blank value
<status>ACTIVE</status>
</user_identifier>

KNOWN FIX


Barcode (if different from EmplID) not included in patron load

If your campus uses a barcode value as an additional identifier, your PeopleSoft administrator will need to add a COMR exception to the Alma PeopleSoft integration provided by the Chancellor's Office to put barcode values into the user extract. Example XML for each user:


<user_identifiers>

.....

<user_identifier segment_type="External">
<id_type desc="Barcode">BARCODE</id_type>
<value>99999999999999</value>
<status>ACTIVE</status>
</user_identifier>

....

</user_identifiers>

CSUN has developed a COMR exception for this, though the barcode is actually not stored in PeopleSoft but rather algorithmically generated based on emplID. Contact Sondra Baier (sondra.baier at csun.edu) at CSUN for more information and example code.

KNOWN FIX


Network login ID (if different from EmplID) not included in patron load

If your campus uses a network login name that you need stored in Alma for authentication purposes (e.g., for EZProxy or ILLiad scripts which send login values to the Alma User API to check Alma user record characteristics/active status/user group type), this data is not by default pulled from PeopleSoft.

Your PeopleSoft administrator will need to add a COMR exception to the Alma PeopleSoft integration provided by the Chancellor's Office to put network user identifier values into the user extract. Example XML for each user:

<user_identifiers>

....

<user_identifier segment_type="External">
<id_type desc="Additional ID 2">OTHER_ID_2</id_type>
<value>dlk22533</value>
<status>ACTIVE</status>
</user_identifier>

.....

</user_identifiers>

CSUN has developed a COMR exception for this. Contact Sondra Baier (sondra.baier at csun.edu) at CSUN for more information and example code.

KNOWN FIX


PeopleSoft Program / Career Code not included in patron load as statistical category

While Dept/major is included in the default program from the Chancellor's Office, PeopleSoft 'career' or program is not. If you wish to include this data (for example, to identify doctoral students), your PeopleSoft administrator will need to add a COMR exception to the Alma PeopleSoft integration provided by the Chancellor's Office. Example XML for each user:

<user_statistics>

....

<user_statistic segment_type="External">
<statistic_category>ABACC</statistic_category>
<statistic_note>PROGRAM</statistic_note>
</user_statistic>

...

</user_statistics>


KNOWN FIX


  • No labels