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

Multiple data provider guidance #1449

Closed
4 tasks done
JimMadge opened this issue Apr 24, 2023 · 0 comments · Fixed by #1707
Closed
4 tasks done

Multiple data provider guidance #1449

JimMadge opened this issue Apr 24, 2023 · 0 comments · Fixed by #1707
Assignees
Labels
documentation Improvements to documentation
Milestone

Comments

@JimMadge
Copy link
Member

✅ Checklist

  • I have searched open and closed issues for duplicates
  • This is a request for a change to documentation
  • This isn't a feature request or bug report
  • This isn't an open-ended question (open a discussion if it is).

📒 Where is the problem?

Related discussion: #1448

Having multiple data providers could cause a number of issues we haven't documented guidance for. In particular,

  • One data provider may see the directories/filenames of another data provider
  • One data provider may overwrite the directories/files of another data provider

📝 Required documentation changes

  • Guidance for best practice to avoid this problems including,
    • Don't use identifiable/sensitive data in file or directory names
    • How to avoid name clashes (e.g. give each provider a unique base directory)
  • (Potentially) document workarounds for dealing with multiple providers (e.g. one share per provider and merge)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants