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

Add streamlined data policy #27

Merged
merged 5 commits into from
Jul 22, 2024
Merged

Add streamlined data policy #27

merged 5 commits into from
Jul 22, 2024

Conversation

lkluft
Copy link
Contributor

@lkluft lkluft commented May 22, 2024

This PR builds heavily on the work in #26, but aims for a more streamlined version of the data policy. While the content of the policy remains the same, the general structure is less rule-based and attempts to merely motivate the ideas.

@lkluft lkluft mentioned this pull request May 22, 2024
@d70-t
Copy link
Collaborator

d70-t commented Jul 3, 2024

The current proposed ORCESTRA data policy is now open to public discussion since about 1.5 months and there are still no objections to this policy. I'd suggest to merge the current proposal if no further objections arise in the next days. If needed, further changes to the proposed policy could be proposed in new pull requests afterwards.

orcestra_book/data_policy.md Outdated Show resolved Hide resolved
orcestra_book/data_policy.md Outdated Show resolved Hide resolved
Copy link
Contributor

@yu71ng yu71ng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Proposed change of the acknowledgement.


For publications using ORCESTRA data, please include this acknowledgement:

> "The data used in this publication was collected during the ORCESTRA field campaign and is available through [insert institute name]. ORCESTRA is supported by the European Space Agency (ESA), the Max Planck Society (MPG), the German Research Foundation (DFG), the German Aerospace Center (DLR), the German Federal Ministry for Education and Research (BMBF), and the US National Science Foundation (NSF)."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> "The data used in this publication was collected during the ORCESTRA field campaign and is available through [insert institute name]. ORCESTRA is supported by the European Space Agency (ESA), the Max Planck Society (MPG), the German Research Foundation (DFG), the German Aerospace Center (DLR), the German Federal Ministry for Education and Research (BMBF), and the US National Science Foundation (NSF)."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the suggested changes, I would have no idea what to put into the acknowledgements 🤷‍♂️

Copy link
Contributor

@yu71ng yu71ng Jul 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about the following to keep it more generic like the rest of the policy:

Suggested change
> "The data used in this publication was collected during the ORCESTRA field campaign and is available through [insert institute name]. ORCESTRA is supported by the European Space Agency (ESA), the Max Planck Society (MPG), the German Research Foundation (DFG), the German Aerospace Center (DLR), the German Federal Ministry for Education and Research (BMBF), and the US National Science Foundation (NSF)."
> "The data used in this publication was collected during the ORCESTRA field campaign and is available through [insert institute name]. ORCESTRA acknowledges support from European, North American, Barbadian and Cape Verdian institutions and funding agencies."

I tried fine tuning the wording, I am not sure it is better, but have a look.  In the end I changed my mind and thought that a listing of the overarching institutions supporting/funding the project would probably save us lots of hassle later on, but I ordered these a bit by my sense of their initiating role.   Please feel free to nit pick
@yu71ng
Copy link
Contributor

yu71ng commented Jul 22, 2024

Hello,
since it appears that so far no ones has big opinions against the PR here, shall we put the updated Data policy online for now?

@yu71ng yu71ng merged commit 2b435f4 into orcestra-campaign:main Jul 22, 2024
2 checks passed
@lkluft lkluft deleted the add-data-policy branch August 5, 2024 07:22
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

Successfully merging this pull request may close these issues.

4 participants