search

MFEh2o / db

**Contains the main issue tracker for the MFE DB!** Functions for interacting with the MFE database, in script format. (See also MFEUtilities, which is an R package that includes many/most of the same functions).
1 stars 0 forks source link

MANIPULATIONS add table #6

Open ctsolomon opened 5 years ago

ctsolomon commented 5 years ago

We need to add a new table that summarizes manipulations made on lakes - start and end dates, what was done, maybe other columns.

ctsolomon commented 5 years ago

Consider also whether to add a flag of some kind to any data point that comes from a manipulated lake

katiesaunders commented 5 years ago

A table format has been finalized, but we haven't decided whether to flag data in some way to indicate a manipulation or to include a disclaimer in the database metadata. I added the documents with information for this table to a folder on Box: MFE>Database>Future MANIPULATIONS table docs.

kaijagahm commented 4 years ago

@ctsolomon are you the CS who made comments on this file: https://app.box.com/file/474630271476? I'm working on adding descriptions of these manipulations to a draft of a MANIPULATIONS table, and it looks like there's still some information that needs to be added/corrected. I've started a doc for MANIPULATIONS here, if you think you can clear up any of the comments or direct me to someone who would know.

kaijagahm commented 4 years ago

Draft of a MANIPULATIONS table is complete. Need people to add/fix things (red and yellow highlights).

ctsolomon commented 4 years ago

Yes, that CS is me. For things like the GPS coordinates of curtain end points - you could ask Randi to coordinate having someone on the field crew do this next time they are at the lake with a little time on their hands. For the other comments that I flagged on the first two Long manipulations, we could check whether Stuart remembers.

I filled in and replied to comments on your Google spreadsheet as best I could, still would be useful to have Stuart and perhaps others take a look.

kaijagahm commented 4 years ago

Randi filled in the coordinates for me.

Just waiting on confirmation/additional info, and discussion of general philosophy re: manipulations.

kaijagahm commented 4 years ago

Consider also whether to add a flag of some kind to any data point that comes from a manipulated lake At meeting 7/7/20, we decided not to add a flag.

A couple more questions @joneslabND @ctsolomon:

  1. We currently have dateStart and dateEnd columns in MANIPULATIONS. Are those designed to refer to the start/end date of the manipulation itself (e.g. if it took more than one day to remove a beaver dam? I don't know) or to the duration of the manipulation if applicable (e.g. how long a curtain stayed in place)? If the latter, which I think is more likely, what should we do for "point" manipulations, like dam removals that may have effects down the line for some unspecified length of time?

My instinct would be to include an end date only when it makes sense unequivocally, e.g. removing a curtain that had been installed. Otherwise leave it as NA. Does that seem reasonable?

  1. I've put the link to the google sheets table out to the Slack. Could you also send that link out to past grad students or anyone else who you think might have information to add?
ctsolomon commented 4 years ago

Hmm, that's a good question. We imagined those columns in the context of things like the curtain installation - so you know the date it goes in and the date it goes out. For something like a one-day beaver dam removal, I think I would enter the same date in both columns. Philosophy here: the manipulation is the thing that you actively do to the lake, like put a curtain in or pull a beaver dam out. There might be long-lasting effects of that manipulation which extend beyond the "dateEnd", but that's not what we're recording here - we're recording "what are the dates when we did something to the lake". What do others think about that approach?

joneslabND commented 4 years ago

I agree with Chris's philosophy. On dam removals we should put the same date for start and end dates

kaijagahm commented 3 years ago

@joneslabND @ctsolomon I'll be doing a database update this week, which would provide a convenient time to add this table to the database. Do you think you might have time to look over what we have and settle on a first version by, say, Thursday afternoon? No worries if not, just let me know whether I should wait or go ahead without this issue.

ctsolomon commented 3 years ago

This might be a good thing for me and Stuart to work through together when we’re both at UNDERC in July. I’ll make a note in my calendar for that week. For now you should go ahead and push a database update without this table.

From: Kaija Gahm @.> Sent: Tuesday, May 25, 2021 1:37 PM To: MFEh2o/db @.> Cc: Chris Solomon @.>; Mention < @.> Subject: Re: [MFEh2o/db] MANIPULATIONS add table (#6)

@joneslabND https://github.com/joneslabND @ctsolomon https://github.com/ctsolomon I'll be doing a database update this week, which would provide a convenient time to add this table to the database. Do you think you might have time to look over what we have and settle on a first version by, say, Thursday afternoon? No worries if not, just let me know whether I should wait or go ahead without this issue.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MFEh2o/db/issues/6#issuecomment-848077027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB74VZELU7HJU3YYOOXMKDLTPPN4XANCNFSM4G7SYATQ .[image: Image removed by sender.]

kaijagahm commented 3 years ago

Status of this one: Stuart and Chris will work on finalizing and adding this table when they have time. The most up-to-date draft is still MANIPULATIONS. I've given ownership of that google sheet to Chris.