-
Notifications
You must be signed in to change notification settings - Fork 2
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
The partner has switched to a new provider and has sent Learning Agreements that were in the First Version. #49
Comments
Thank you Anant for creating this issue. Could you please upload here the last version of LA created under the old provider and the first one created under the new provider (of course with anonymised private data). In particular I would like to see which identifiers are reused which allow to recognize this LA as the old one. |
Updated the question with example, steps and questions |
Yes. This LA has all three signatures from proper persons. Provider does not matter (from the business point of view).
Yes, it can. |
but Provider2 will not have any history of the action taken on learning agreement. |
That's true, but will this be a problem? Can you show an example when this will matter. |
How to the receiver knows that the LA received is genuine ? |
Because it comes from the server covering the sending hEI. |
What Anant meant is the genuineness of the receiver signature added on the LA by the sending HEI. |
I understand that you mean this part of LA:
'signer-app' where the name of the Provider is given has no business value. If HEI get LA from the proper node, with the proper signer name, position, email, it can assume that this is the valid LA, the same as the one obtained from the other provider. In particular 'signer-app' is optional. |
Does it mean that the LA can be moved to first version even if receiving institution has not approved, since it is not mandatory? |
It is mandatory, only signer-app is not important. |
|
I am not sure if you have understood the question. Question is how can my system trust that the LA was indeed signed by my client? Anyone in the network can send me a LA claiming that it was signed by me, on so and so date. |
This is not anyone. This is the provider who represents your partner. I do not see any added value in the signer-app having any particular value. Anyone can put any value there or leave it empty.
To prove what and how? I just do not follow :( |
As I understand, no proof of any sort is needed in terms of whether receiving institution has signed the LA or nor, as long as sending institution is claiming that the receiving institution signed it on a particular date. Thanks for confirming. We will follow that. This thread can be closed. |
|
Receiving HEI knows whether it has approved LA under Provider 1, this knowledge is moved to Provider 2, so Receiving HEI still knows that LA has been approved. |
This is one of the issues to discus within the general Data Portability context. I will raise it during the IF meeting on 2024-07-17. |
We have a case where the partner changed providers and then sent us the LA from First version onwards i.e. no changes proposal was present. Is this acceptable? Can they continue to make changes post the first version?
Steps
Question: Can Provider 2 assume that the LA is valid since they do not have the original approval or history?
Question 2: Can this LA be further edited i.e. post first version? Since the sending institution has not changed their provider, they should not have any problems in updating their LA.
The text was updated successfully, but these errors were encountered: