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

Update DataverseNO affiliations file #42

Open
philippconzett opened this issue May 22, 2022 · 4 comments
Open

Update DataverseNO affiliations file #42

philippconzett opened this issue May 22, 2022 · 4 comments
Assignees

Comments

@philippconzett
Copy link

Task:
@4tikhonov @Louis-wr An updated version of the DataverseNO affiliation file (dvnoaffiliations.tsv or dvnoaffiliations.txt) needs to be uploaded to dataverse.no, demo.dataverse.no, and test.dataverse.no. The files can be found in Teams >> Shiboleth >> Files.

Question:
How does the trigger solution differentiate between email addresses that have identical last parts?

Easy case:
@Student.uio.no
@sv.uio.no
@Student.uio.no

They are all addresses from the same organisation (UiO) and should all be assigned to the uio.no user group.

Tricky case:
@norsus.no
@sus.no

They are addresses from two different organisations (Norsus and SUS). @norsus.no needs to be assigned to the norsus.no user group, whereas @sus.no needs to be assigned to the sus.no user group.

@Louis-wr
Copy link

location :
/distrib/private/affiliations.csv
/root/distrib/5.8/dataverse-docker/affiliation2data.py
vi /root/distrib/5.8/dataverse-docker/affiliations.sql

@philippconzett
Copy link
Author

Question: How is this issue resolved?

@philippconzett
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants