-
Notifications
You must be signed in to change notification settings - Fork 32
Milestones
List view
Concisely describe the motivation, context and use of the EML package. Paper in the style of MEE Application notes, PLOS Comp Bio, or Ecosphere's Emerging Tech.
Due by September 1, 2019•1/1 issues closed- Due by September 30, 2018•9/9 issues closed
- Due by June 1, 2019•6/8 issues closed
Primarily low-level API and performance issues
Due by January 1, 2018•4/4 issues closedCRAN release should provide a stable API for working with metadata for `data.frame` objects. Functionality should be up to the level put forward in manuscript draft and examples. In particular, we need to improve examples for handling coverage metadata, accessing and searching across multiple EML files, publishing and downloading from KNB, and illustrating some useful functionality on attribute-level metadata. A proof-of-principle showing semantic extensions would also be good.
Due by December 31, 2016•23/23 issues closedShould define an extension of data.frame to which metadata can be added and still manipulated as a data.frame. This also provides the framework for eml_read by defining an easier object for users to interact with once EML has been read in than just working with the `eml` S4 class. In addition to acting like a `data.frame`, this object has methods such as `show`, `contact`, `dataTable`, `citationInfo()` etc to interact with it's metadata (see 'read' section of ReadMe). More methods will be added. This milestone marks the stable API for working with `data.frame` objects in EML. This freezes the interface for creating minimal EML objects and the interface for manipulating EML data tables.
No due date•2/2 issues closedNow that we have a proof-of-concept in place that generates valid EML, there are quite a few fields that we should be populating automatically from the R object data, even though they are strictly optional (e.g. #16, numberOfRecords). Issues addressing these cases (for dataTable objects at the moment) should be added to this milestone. There are also some fields that appear in most EML, though not strictly required to validate. Perhaps chief among these is the EML <coverage> node. Issues introducing other crucial if not required nodes should likewise be added to this milestone.
No due date•4/4 issues closedHave in place all functions to illustrate a complete proof-of-concept: - Generate EML from an R data.frame - Publish the EML to an external server (e.g. figshare, github) - Read in the EML from an external server into an R data frame and metadata list objects.
No due date•5/5 issues closed