Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patron entity addition - Parental Consent / Internet Flag #58

Closed
Neil-IMIL opened this issue Apr 12, 2017 · 3 comments
Closed

Patron entity addition - Parental Consent / Internet Flag #58

Neil-IMIL opened this issue Apr 12, 2017 · 3 comments

Comments

@Neil-IMIL
Copy link

Request for additional information about the borrowers in the patron entity. The request is to include existing functionality implemented by most of the UK main LMS's where additional information from the borrower record is returned via extensions to the current SIP2 response 64 and in newer subsequent web services implementations. This functionality relates to Parental Consent / internet access, although referred to in different ways by different systems and authorities, and provides in the main implementation a yes, no or null response / value for each borrower. This information is used along with other borrower specific information to authorise a user after authentication to determine if the requested functionality is available to the current user

@franciscave
Copy link
Collaborator

Matthew, are you able to advise how this is handled in the NISO SIP3 proposals? It would be good to adopt a compatible approach. Anthony, do you have views on this? Is it sufficient to have a code list with two values: 'Yes' and 'No'? The value 'unspecified/unknown' could be represented simply by the field/element being omitted.

@mdovey
Copy link
Collaborator

mdovey commented Jul 4, 2017

SIP3 added patron type ["such as child, adult, juvenile"] but nothing more.

Might be special case of #55

@mdovey
Copy link
Collaborator

mdovey commented Jan 31, 2018

Closed as special case of #55

@mdovey mdovey closed this as completed Jan 31, 2018
@mdovey mdovey added this to the 1.0.1 milestone Feb 2, 2018
@mdovey mdovey removed this from the 1.0.1 milestone Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants