#10 Anonymous access link/token for journal editor/review

닫힘
pgoltstein6 년 전을 오픈 · 2개의 코멘트
Pieter Goltstein 코멘트됨, 6 년 전

Hi,

First of all, great initiative! I've already been using github for a while and this seems like the perfect interface for making experimental data publicly accessible.

Nowadays, journals often like to directly see the source data and pass on access to anonymous reviewers. A feature that might be very useful to add would be to have an option to grant access to a single private repository using a private link or access token. I have no idea how to implement this, but it would be great if this was possible or if anyone can help me set this up if it is already possible.

Many thanks, Pieter

Hi, First of all, great initiative! I've already been using github for a while and this seems like the perfect interface for making experimental data publicly accessible. Nowadays, journals often like to directly see the source data and pass on access to anonymous reviewers. A feature that might be very useful to add would be to have an option to grant access to a single private repository using a private link or access token. I have no idea how to implement this, but it would be great if this was possible or if anyone can help me set this up if it is already possible. Many thanks, Pieter
Christian Garbers 코멘트됨, 6 년 전
협업자

Hey Pieter!!

First of all, great initiative! I've already been using github for a while and his seems like the perfect interface for making experimental data publicly accessible.

Thanks, its such words that keep us going!

Nowadays, journals often like to directly see the source data and pass on access to anonymous reviewers. A feature that might be very useful to add would be to have an option to grant access to a single private repository using a private link or access token. I have no idea how to implement this, but it would be great if this was possible or if anyone can help me set this up if it is already possible.

Agreed, and we have been thinking about this. However, currently its a bit hard impossible to implement access without an account or access tokens created per repository...

Here are several workarounds:

  • Just create an account using another email address (can be deleted later - maybe add the reason in the user description). For that user, an access token might be created and/or the password provided with the submission. Then share the repository with that user.
  • You might also consider to just share invite the repository with a secondary email address and accept it. This way the sharing is setup automatically. Anything else as above
  • Make the repository public but don't list it (not really save - but maybe good enough for many cases).

Hope that helps a bit!

All the Best

Christian

Hey Pieter!! >First of all, great initiative! I've already been using github for a while and his seems like the perfect interface for making experimental data publicly accessible. Thanks, its such words that keep us going! >Nowadays, journals often like to directly see the source data and pass on access to anonymous reviewers. A feature that might be very useful to add would be to have an option to grant access to a single private repository using a private link or access token. I have no idea how to implement this, but it would be great if this was possible or if anyone can help me set this up if it is already possible. Agreed, and we have been thinking about this. However, currently its a bit hard ~~impossible~~ to implement access without an account or access tokens created per repository... Here are several workarounds: * Just create an account using another email address (can be deleted later - maybe add the reason in the user description). For that user, an access token might be created and/or the password provided with the submission. Then share the repository with that user. * You might also consider to just [share invite the repository](https://web.gin.g-node.org/G-Node/Info/wiki/WebInterface#collaboration) with a secondary email address and accept it. This way the sharing is setup automatically. Anything else as above * Make the repository public but don't list it (not really save - but maybe good enough for many cases). Hope that helps a bit! All the Best Christian
Pieter Goltstein 코멘트됨, 6 년 전
포스터

Hey Christian, Thanks a lot for the rapid reply and the info, I can work with that. Cheers, Pieter

Hey Christian, Thanks a lot for the rapid reply and the info, I can work with that. Cheers, Pieter
로그인하여 이 대화에 참여
마일스톤 없음
담당자 없음
참여자 2명
로딩중...
취소
저장
아직 콘텐츠가 없습니다.