General guidelines for different cases

[snahdog]

I am new to learning about ODM2. I am intrigued by it because it seems to be very flexible, allows a large amount of customization, and could be configured to deal with many custom and unique situations. The downside of this is that it may be a little overwhelming for beginners. Is there a document with general guidelines for common use cases or best practices that users can refer to? If not, is it possible to create one that people can add to over time as they apply ODM2?

For instance, a common use case would be to represent a network of gages (say stream gages) with multiple gages being installed at a different locations in space. A user may want to represent such a network in a GIS system or just allow other to retrieve data from one or multiple gages. Based on my understanding of ODM2, the way to do this would be to make individual Sampling Features/Actions/Results for each gage and then use a Dataset to tie it all together. Is this the correct approach? One one hand, it seems like this would get the job done. On the other hand, it seems a little counter-intuitive because the aggregation of the gages into a network is done at the results level and not at the physical level (i.e. Sampling Feature). It would be good to get guidance on such common cases so that new users can feel more confident.

[snahdog]

I wanted to add that I am specifically asking about implementing different situations. I know that there are documents on best practices for things such as handling dates, no data, etc. I am more interested in a document that presents implementations, i.e. something that answers the following questions for many different cases:

What are we trying to do? ("represent a stream gage network")
How did we implement it? ("we created these following Samplingfeatures/Actions/Results., etc.")