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

Creating private issues for student data archival requests! #2866

Open
balajialg opened this issue Oct 11, 2021 · 5 comments
Open

Creating private issues for student data archival requests! #2866

balajialg opened this issue Oct 11, 2021 · 5 comments
Assignees
Labels
file services Disk, filestore, NFS, usage process Processes that need to be developed

Comments

@balajialg
Copy link
Contributor

balajialg commented Oct 11, 2021

Summary

Currently, our data archival requests are out to the public. It may not be an ideal scenario as all the student email details are publicly accessible which may not align with FERPA requirements. We should explore creating private issues for such requests so that student details are held privately.

My initial exploration led me to find this github issue to allow private issues in a public repository. Despite this being a feature requested way back in 2013, Github has not solved it, unfortunately (at least based on my current understanding). So creating this issue to explore alternate scenarios where such requests details are held private by using other suggested options such as GitLab or creating a private repository to handle this issue from now on.

Tasks to complete

  1. Explore alternatives to keep student data private
  2. Implement the feasible solution
@balajialg balajialg self-assigned this Oct 11, 2021
@balajialg balajialg changed the title Allowing private issues for student data archival requests! Creating private issues for student data archival requests! Oct 11, 2021
@balajialg balajialg added the process Processes that need to be developed label Oct 11, 2021
@balajialg
Copy link
Contributor Author

balajialg commented Oct 18, 2021

@felder's suggestion is to move such requests to a ticketing system of choice - Service Now or JIRA. To be discussed during the November sprint planning meeting.

@yuvipanda
Copy link
Contributor

Yeah, this was the reason I had initially used the email address in the note.

@flawnn
Copy link

flawnn commented Nov 22, 2021

A bit off topic:
But I created a thread in GitHub Discussions to get that feature implemented.
community/community#7971

@balajialg
Copy link
Contributor Author

balajialg commented Nov 23, 2021

Thanks a lot, @flawnn for starting the discussion again. Hoping that GitHub prioritizes this feature soon.

Thanks for giving us a heads-up! Appreciate it.

@felder
Copy link
Contributor

felder commented Nov 23, 2021

@flawnn thanks! I wonder if github even has any interest in solving this issue though. "Privacy" is something github charges for, although I guess I could see them including this feature in paid plans.

We also do have plans to automate this in the future so that students can securely obtain their files and they don't have to wait for support to do the retrieval.

@ryanlovett ryanlovett added the file services Disk, filestore, NFS, usage label Dec 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
file services Disk, filestore, NFS, usage process Processes that need to be developed
Projects
None yet
Development

No branches or pull requests

5 participants