Add attribution metadat policy for BIG_DATA

[Yaswant Pradhan (yaswant)]

PR Summary

IAO Approver: Ben Fitzpatrick (@benfitzpatrick)
Code Reviewer: Sam Clarke-Green (@t00sa)

Cc: Andrew Clark (@arjclark)

Adding attribution metadata policy to working practices.

Code Quality Checklist

• I have performed a self-review of my own code
• I have locally built the documentation successfully, and the output of changed sections is as expected https://wwwspice/~yaswant.pradhan/simulation-systems/big-data-policy/html/Reviewers/howtocommit.html

IAO Comments

Code Review

• The changes are coherent and valid

[Sam Clarke-Green (t00sa)]

This is a good start, but there are no rules for developers. Without clear guidance on what sort of data can be added and what the supporting evidence is required, this will result in more problems during review.

The PR also seems to be doing two things: adding information about the big data policy, and fixing typos and changing build instructions in other sections. These are separate and the second part needs to be split out into another PR.

[Yaswant Pradhan (yaswant)]

Good points, Sam Clarke-Green (@t00sa) - I initially thought this would be best placed in the Developer section, but since the reference to BIG_DATA was only in the Reviewer section, that's where it ended up. You're correct that some adjustments are needed. Regarding what's permitted, ANCILDIR-Deploy should be considered the single source of truth.

I'll revert the typo and jules-doc compilation updates and address them in another PR.

[Ben Fitzpatrick (benfitzpatrick)]

Ah, one issue might be that collaborators can't see this one - it's deliberately not collaborator visible. Andy is happy that you extract / quote it here if you want.

[Yaswant Pradhan (yaswant)]

Thanks both.

Moved the guidance to development checklist section. Included process (extract from ANCILDIR-Deploy) here for wider visibility.

[Sam Clarke-Green (t00sa)]

See comments in-line

[Sam Clarke-Green (t00sa)]

Better not to imply that this is optional:

Suggested change

	Where possible, this should follow existing UM ``ANCILDIR`` conventions (`see
	This should follow existing UM ``ANCILDIR`` conventions (`see

[Yaswant Pradhan (yaswant)]

For LFRic, we prefer to include the metadata and license as NetCDF global attributes rather than storing them separately. This approach does not currently apply to UM ANCILDIR.

For non-NetCDF LFRic files, we follow UM ANCILDIR convention.

[Sam Clarke-Green (t00sa)]

Suggested change

	In cases where a file has been generated from multiple sources, it should be
	made clear where each licence/attribution/acknowledgement has come from.
	In cases where a file has been generated from multiple sources, the liccences
	must be compatible with each other and it should be made clear where each licence/attribution/acknowledgement has come from.