You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<attributeDefinition>the weight (mass) of all items in the net (may be extrapolated)</attributeDefinition>
<attributeDefinition>the weight (mass) of all items in the net, converted to kg/tow for the Albatross research vessel (one two is approximately 0.0384 km^2)</attributeDefinition>
The .xml files follow the Ecological Metadata Language (EML) format, and the scripts use the R package "EML".
I tried to use standardized definitions where applicable. The reason for this is to indicate to readers which columns might be comparable between data sets; if both column names and definitions are idiosyncratic, it can be difficult to follow. For this reason, I use the gen.cols&units.R script to provide template/ standardized units and definitions.
The item you've corrected is on the line with the text "BIOMASS" = gen.cols[["weight"]]; instead of subsetting gen.cols, a custom definition could be written. There might be a way to add a note or comment to a data field (in addition to a description and units), that way we could keep the standard descriptions and units (so it is easier to compare data sets). But it's been a while since I did this, so I don't know/ forget.
On Mon, Jan 23, 2017 at 4:26 PM, Ryan Batt ***@***.***> wrote:
Actually, the .xml files are generated from simpler R scripts; for
example: https://github.com/mpinsky/OceanAdapt/blob/master/R/
metadata/metaData.neus.R
The .xml files follow the Ecological Metadata Language (EML) format, and
the scripts use the R package "EML".
I tried to use standardized definitions where applicable. The reason for
this is to indicate to readers which columns might be comparable between
data sets; if both column names and definitions are idiosyncratic, it can
be difficult to follow. For this reason, I use the gen.cols&units.R script
to provide template/ standardized units and definitions.
The item you've corrected is on the line with the text "BIOMASS" =
gen.cols[["weight"]]
<https://github.com/mpinsky/OceanAdapt/blob/master/R/metadata/metaData.neus.R#L43>;
instead of subsetting gen.cols, a custom definition could be written.
There might be a way to add a note or comment to a data field (in addition
to a description and units), that way we could keep the standard
descriptions and units (so it is easier to compare data sets). But it's
been a while since I did this, so I don't know/ forget.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<1df891d#commitcomment-20581993>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGE05LPQdKeqCkcawmL9X99R7mYOW7SOks5rVRsQgaJpZM4LgmoB>
.
The reason will be displayed to describe this comment to others. Learn more.
Best option would be to add a "comment" or "note" field to the variable, if
it exists in the EML framework. Otherwise, there should be an overarching
"methods" section that covers similar details for all fields in the neus
data set. I'm basing this off of how NTL LTER organizes their metadata;
they use EML.
On Mon, Jan 23, 2017 at 8:01 PM The Pinsky Lab <[email protected]>
wrote:
What do you suggest we do? I think it's important that we record this
detail of the dataset.
On Mon, Jan 23, 2017 at 4:26 PM, Ryan Batt ***@***.***>
wrote:
> Actually, the .xml files are generated from simpler R scripts; for
> example: https://github.com/mpinsky/OceanAdapt/blob/master/R/
> metadata/metaData.neus.R
>
> The .xml files follow the Ecological Metadata Language (EML) format, and
> the scripts use the R package "EML".
>
> I tried to use standardized definitions where applicable. The reason for
> this is to indicate to readers which columns might be comparable between
> data sets; if both column names and definitions are idiosyncratic, it can
> be difficult to follow. For this reason, I use the gen.cols&units.R
script
> to provide template/ standardized units and definitions.
>
> The item you've corrected is on the line with the text "BIOMASS" =
> gen.cols[["weight"]]
> <
https://github.com/mpinsky/OceanAdapt/blob/master/R/metadata/metaData.neus.R#L43
>;
> instead of subsetting gen.cols, a custom definition could be written.
> There might be a way to add a note or comment to a data field (in
addition
> to a description and units), that way we could keep the standard
> descriptions and units (so it is easier to compare data sets). But it's
> been a while since I did this, so I don't know/ forget.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <
1df891d#commitcomment-20581993
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AGE05LPQdKeqCkcawmL9X99R7mYOW7SOks5rVRsQgaJpZM4LgmoB
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<1df891d#commitcomment-20584897>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXrf_BYiqBY1XBfOfI11lVnGZI6beirks5rVU1cgaJpZM4LgmoB>
.
On Tue, Jan 24, 2017 at 8:05 AM, Ryan Batt ***@***.***> wrote:
Best option would be to add a "comment" or "note" field to the variable, if
it exists in the EML framework. Otherwise, there should be an overarching
"methods" section that covers similar details for all fields in the neus
data set. I'm basing this off of how NTL LTER organizes their metadata;
they use EML.
On Mon, Jan 23, 2017 at 8:01 PM The Pinsky Lab ***@***.***>
wrote:
> What do you suggest we do? I think it's important that we record this
>
>
> detail of the dataset.
>
>
>
>
>
> On Mon, Jan 23, 2017 at 4:26 PM, Ryan Batt ***@***.***>
> wrote:
>
>
>
>
>
> > Actually, the .xml files are generated from simpler R scripts; for
>
>
> > example: https://github.com/mpinsky/OceanAdapt/blob/master/R/
>
>
> > metadata/metaData.neus.R
>
>
> >
>
>
> > The .xml files follow the Ecological Metadata Language (EML) format,
and
>
>
> > the scripts use the R package "EML".
>
>
> >
>
>
> > I tried to use standardized definitions where applicable. The reason
for
>
>
> > this is to indicate to readers which columns might be comparable
between
>
>
> > data sets; if both column names and definitions are idiosyncratic, it
can
>
>
> > be difficult to follow. For this reason, I use the gen.cols&units.R
> script
>
>
> > to provide template/ standardized units and definitions.
>
>
> >
>
>
> > The item you've corrected is on the line with the text "BIOMASS" =
>
>
> > gen.cols[["weight"]]
>
>
> > <
> https://github.com/mpinsky/OceanAdapt/blob/master/R/
metadata/metaData.neus.R#L43
> >;
>
>
> > instead of subsetting gen.cols, a custom definition could be written.
>
>
> > There might be a way to add a note or comment to a data field (in
> addition
>
>
> > to a description and units), that way we could keep the standard
>
>
> > descriptions and units (so it is easier to compare data sets). But it's
>
>
> > been a while since I did this, so I don't know/ forget.
>
>
> >
>
>
> > —
>
>
> > You are receiving this because you commented.
>
>
> > Reply to this email directly, view it on GitHub
>
>
> > <
> https://github.com/mpinsky/OceanAdapt/commit/1df891d#commitcomment-20581993
> >,
>
>
> > or mute the thread
>
>
> > <
> https://github.com/notifications/unsubscribe-auth/
AGE05LPQdKeqCkcawmL9X99R7mYOW7SOks5rVRsQgaJpZM4LgmoB
> >
>
>
> > .
>
>
> >
>
>
>
>
>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/mpinsky/OceanAdapt/commit/1df891d#commitcomment-20584897>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFXrf_
BYiqBY1XBfOfI11lVnGZI6beirks5rVU1cgaJpZM4LgmoB>
> .
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<1df891d#commitcomment-20590925>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGE05CvM1TCcnPv1FKgjdXffb6QFV95pks5rVfb_gaJpZM4LgmoB>
.
Thanks, Ryan. Please make that edit, as you know EML much better than I do.
On Tue, Jan 24, 2017 at 8:05 AM, Ryan Batt ***@***.***>
wrote:
> Best option would be to add a "comment" or "note" field to the variable,
if
> it exists in the EML framework. Otherwise, there should be an overarching
> "methods" section that covers similar details for all fields in the neus
> data set. I'm basing this off of how NTL LTER organizes their metadata;
> they use EML.
> On Mon, Jan 23, 2017 at 8:01 PM The Pinsky Lab ***@***.***
>
> wrote:
>
> > What do you suggest we do? I think it's important that we record this
> >
> >
> > detail of the dataset.
> >
> >
> >
> >
> >
> > On Mon, Jan 23, 2017 at 4:26 PM, Ryan Batt ***@***.***>
> > wrote:
> >
> >
> >
> >
> >
> > > Actually, the .xml files are generated from simpler R scripts; for
> >
> >
> > > example: https://github.com/mpinsky/OceanAdapt/blob/master/R/
> >
> >
> > > metadata/metaData.neus.R
> >
> >
> > >
> >
> >
> > > The .xml files follow the Ecological Metadata Language (EML) format,
> and
> >
> >
> > > the scripts use the R package "EML".
> >
> >
> > >
> >
> >
> > > I tried to use standardized definitions where applicable. The reason
> for
> >
> >
> > > this is to indicate to readers which columns might be comparable
> between
> >
> >
> > > data sets; if both column names and definitions are idiosyncratic, it
> can
> >
> >
> > > be difficult to follow. For this reason, I use the gen.cols&units.R
> > script
> >
> >
> > > to provide template/ standardized units and definitions.
> >
> >
> > >
> >
> >
> > > The item you've corrected is on the line with the text "BIOMASS" =
> >
> >
> > > gen.cols[["weight"]]
> >
> >
> > > <
> > https://github.com/mpinsky/OceanAdapt/blob/master/R/
> metadata/metaData.neus.R#L43
> > >;
> >
> >
> > > instead of subsetting gen.cols, a custom definition could be written.
> >
> >
> > > There might be a way to add a note or comment to a data field (in
> > addition
> >
> >
> > > to a description and units), that way we could keep the standard
> >
> >
> > > descriptions and units (so it is easier to compare data sets). But
it's
> >
> >
> > > been a while since I did this, so I don't know/ forget.
> >
> >
> > >
> >
> >
> > > —
> >
> >
> > > You are receiving this because you commented.
> >
> >
> > > Reply to this email directly, view it on GitHub
> >
> >
> > > <
> > https://github.com/mpinsky/OceanAdapt/commit/
> 1df891d#commitcomment-20581993
> > >,
> >
> >
> > > or mute the thread
> >
> >
> > > <
> > https://github.com/notifications/unsubscribe-auth/
> AGE05LPQdKeqCkcawmL9X99R7mYOW7SOks5rVRsQgaJpZM4LgmoB
> > >
> >
> >
> > > .
> >
> >
> > >
> >
> >
> >
> >
> >
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/mpinsky/OceanAdapt/commit/
> 1df891d#commitcomment-20584897>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AFXrf_
> BYiqBY1XBfOfI11lVnGZI6beirks5rVU1cgaJpZM4LgmoB>
>
> > .
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/mpinsky/OceanAdapt/commit/1df891d#commitcomment-20590925>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
AGE05CvM1TCcnPv1FKgjdXffb6QFV95pks5rVfb_gaJpZM4LgmoB>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<1df891d#commitcomment-20599512>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFXrf9h8GXb-Vadm9u6iK3TTTUy0XqYTks5rVmSDgaJpZM4LgmoB>
.
On Tue, Jan 24, 2017 at 3:56 PM, Ryan Batt ***@***.***> wrote:
Not sure what options we actually have, but I'll look into it.
On Tue, Jan 24, 2017 at 3:52 PM, The Pinsky Lab ***@***.***>
wrote:
> Thanks, Ryan. Please make that edit, as you know EML much better than I
do.
>
>
> On Tue, Jan 24, 2017 at 8:05 AM, Ryan Batt ***@***.***>
> wrote:
>
> > Best option would be to add a "comment" or "note" field to the
variable,
> if
> > it exists in the EML framework. Otherwise, there should be an
overarching
> > "methods" section that covers similar details for all fields in the
neus
> > data set. I'm basing this off of how NTL LTER organizes their metadata;
> > they use EML.
> > On Mon, Jan 23, 2017 at 8:01 PM The Pinsky Lab <
***@***.***
> >
> > wrote:
> >
> > > What do you suggest we do? I think it's important that we record this
> > >
> > >
> > > detail of the dataset.
> > >
> > >
> > >
> > >
> > >
> > > On Mon, Jan 23, 2017 at 4:26 PM, Ryan Batt ***@***.***
>
> > > wrote:
> > >
> > >
> > >
> > >
> > >
> > > > Actually, the .xml files are generated from simpler R scripts; for
> > >
> > >
> > > > example: https://github.com/mpinsky/OceanAdapt/blob/master/R/
> > >
> > >
> > > > metadata/metaData.neus.R
> > >
> > >
> > > >
> > >
> > >
> > > > The .xml files follow the Ecological Metadata Language (EML)
format,
> > and
> > >
> > >
> > > > the scripts use the R package "EML".
> > >
> > >
> > > >
> > >
> > >
> > > > I tried to use standardized definitions where applicable. The
reason
> > for
> > >
> > >
> > > > this is to indicate to readers which columns might be comparable
> > between
> > >
> > >
> > > > data sets; if both column names and definitions are idiosyncratic,
it
> > can
> > >
> > >
> > > > be difficult to follow. For this reason, I use the gen.cols&units.R
> > > script
> > >
> > >
> > > > to provide template/ standardized units and definitions.
> > >
> > >
> > > >
> > >
> > >
> > > > The item you've corrected is on the line with the text "BIOMASS" =
> > >
> > >
> > > > gen.cols[["weight"]]
> > >
> > >
> > > > <
> > > https://github.com/mpinsky/OceanAdapt/blob/master/R/
> > metadata/metaData.neus.R#L43
> > > >;
> > >
> > >
> > > > instead of subsetting gen.cols, a custom definition could be
written.
> > >
> > >
> > > > There might be a way to add a note or comment to a data field (in
> > > addition
> > >
> > >
> > > > to a description and units), that way we could keep the standard
> > >
> > >
> > > > descriptions and units (so it is easier to compare data sets). But
> it's
> > >
> > >
> > > > been a while since I did this, so I don't know/ forget.
> > >
> > >
> > > >
> > >
> > >
> > > > —
> > >
> > >
> > > > You are receiving this because you commented.
> > >
> > >
> > > > Reply to this email directly, view it on GitHub
> > >
> > >
> > > > <
> > > https://github.com/mpinsky/OceanAdapt/commit/
> > 1df891d#commitcomment-20581993
> > > >,
> > >
> > >
> > > > or mute the thread
> > >
> > >
> > > > <
> > > https://github.com/notifications/unsubscribe-auth/
> > AGE05LPQdKeqCkcawmL9X99R7mYOW7SOks5rVRsQgaJpZM4LgmoB
> > > >
> > >
> > >
> > > > .
> > >
> > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > —
> > > You are receiving this because you were mentioned.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/mpinsky/OceanAdapt/commit/
> > 1df891d#commitcomment-20584897>,
> > > or mute the thread
> > > <https://github.com/notifications/unsubscribe-auth/AFXrf_
> > BYiqBY1XBfOfI11lVnGZI6beirks5rVU1cgaJpZM4LgmoB>
> >
> > > .
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/mpinsky/OceanAdapt/commit/
> 1df891d#commitcomment-20590925>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/
> AGE05CvM1TCcnPv1FKgjdXffb6QFV95pks5rVfb_gaJpZM4LgmoB>
>
> > .
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/mpinsky/OceanAdapt/commit/1df891d#commitcomment-20599512>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFXrf9h8GXb-
Vadm9u6iK3TTTUy0XqYTks5rVmSDgaJpZM4LgmoB>
> .
>
--
Ryan D. Batt
Aquatic Ecologist
Postdoctoral Researcher, Rutgers University
Website: http://limnology.wisc.edu/personnel/batt/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<1df891d#commitcomment-20599550>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGE05AwZRq2u_nZrpAczHx44pgliWvvmks5rVmVqgaJpZM4LgmoB>
.
1df891dThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rBatt Ryan, did I add this into the metadata correctly? I wanted to document the swept area for the NEUS biomass data.
1df891dThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, the .xml files are generated from simpler R scripts; for example: https://github.com/mpinsky/OceanAdapt/blob/master/R/metadata/metaData.neus.R
The .xml files follow the Ecological Metadata Language (EML) format, and the scripts use the R package "EML".
I tried to use standardized definitions where applicable. The reason for this is to indicate to readers which columns might be comparable between data sets; if both column names and definitions are idiosyncratic, it can be difficult to follow. For this reason, I use the gen.cols&units.R script to provide template/ standardized units and definitions.
The item you've corrected is on the line with the text
"BIOMASS" = gen.cols[["weight"]]; instead of subsettinggen.cols, a custom definition could be written. There might be a way to add a note or comment to a data field (in addition to a description and units), that way we could keep the standard descriptions and units (so it is easier to compare data sets). But it's been a while since I did this, so I don't know/ forget.1df891dThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1df891dThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1df891dThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1df891dThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1df891dThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1df891dThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.