misoproject / dataset Goto Github PK

Currently every value passes through the coercion methods - change that to take in the whole column data array and cast it that way to reduce stack.

Problem with time type returning integer.

Takes a dataset like:

State, 2001, 2002
AZ     2     4
AL     6     7

And normalizes it like so:

ds.rowify( { "year" : ["2001", "2002"]});

State, Year, Value
AZ     2001  2
AZ     2002  4
AL     2001  6
AL     2002  7

Nice to have.

We have some basic view performance tests, but we need more, especially if we are going to start optimizing things in the future.

When there are repetitive string values in a column, replace them with an enum that maps to a lookup table.

A hook where data has been loaded but not typed to manipulate rows/columns.

It should be called as a .set on a dataset and ALL rows in that dataset should be set. This is because we would probably first be filering a dataset down and then setting a value. For example:

dataset.where({ budget : function(value) {
  return value > 100000;
}).set({ huge : true });

move that to the wrapper

We seem to constantly need a set of unique values in a dataset.

ds.rows({ value: 450 });

Will return view of all rows that match the specified object.

At the moment we are passing in { sync : true } to various method to allow one to subscribe to changes on it. This is currently somewhat inconsistant (you can do this on products but not on direct value extractions) and somewhat bulky when you don't want to keep any updates on your data (which unless you have a live data feed, you don't.)

Look into pulling out the sync behavior into a separate mixin that will enable binding to various dataset extraction methods.

When we get a product on a non syncing dataset its a number, otherwise it's a product. Is that confusing?

// syncable ds:
ds.max("pop") => Miso.Product

// non syncable ds:
ds.max("pop") => 14

See internal spec:
https://github.com/alexgraul/dataset/wiki/Internal-event-representation-+-binding

Currently global.DS is set to this at the end of ds.js. Instead, the global.DS should only be set if it doesn't already exist.

Allow for a way to take our normalized & disagregated data and turn it into subset groupings

For example, in a dataset like:

Race  Gender  Wage
W F 100
W M 200
B F 100
B M 200

The following aggregates will be created:

Race  Gender  Wage
W F 100
W M 200

Race  Gender  Wage
B F 100
B M 200

Race  Gender  Wage
B F 100
W F 200

Race  Gender  Wage
B M 100
W M 200

Race  Gender  Wage
* F 200

Race  Gender  Wage
* M 400

Race  Gender  Wage
W * 300

Race  Gender  Wage
B * 300

Race  Gender  Wage
* * 600

Potential syntax:

ds.groupings(
  [
    {name: 'Race', aggregate : true},  
    {name: 'Gender', aggregate : true} 
  ]
);

OR

ds.groupings(['Race', 'Gender'],  {aggregate : true});

On initialization of dataset, specify custom subsets that are cached by subset name + passed arguments:

data = new Dataset({
  url : "http://bla.json",
  subsets : {
    a_state : function(state) {
      return this.filter(function(row) {
        return row.get("state") === state;
      });
    },
    a_state_by_hour : function(state) {
      return this.subset("a_state", state).groupBy("hour")
    },
    a_state_by_type : function(state) {
      return this.subset("a_state", state).groupBy("type")
    }
  }
})

Add support for explicitly setting a column type on import and coercing rows to that type. Add support for a time type which is coerced into moment.js

Test -> coerce. fail otherwise.

Probably copy and paste issue. Currently triggers remove.

Document constructor properties

When passing a format that contains "/", when the regexp is cached, it doesn't return the proper result.

Allows one to group the values in a column based on duplicate values in another. For example:

State Val1  Val2  
AZ  5 6
AZ  10  10

Calling the following

dataset.groupBy("state", ["Val1"])

Which would return:

State Val1
AZ 15

// adds empty column
dataset.addColumn("name");

// adds a column with data
dataset.addColumn("name", [1,2,3,4,5]);

// another way to add data to a column
dataset.addColumn("name").each(function(row) {
  row.name = 12;
});

Should return reference to dataset so we can further chain awesomeness.

Previously calling

dataset.max('budget') 

returned a number.

Now any numeric derived values should return an object that has two methods:

.val()
.bind()

.bind will still bind to the original dataset to all rows that are relevant to the computation.

We noticed many a times we need a particular subset of the data for a component (like all rows pertinent to a state from a dataset that has data to all the states.) Because a component SHOULD be agnostic to its context, it SHOULDN'T be responsible for FIRST filtering the data and THEN extracting the values it needs.

Add the following functionality:

1. Define views on a dataset

var ds = new Dataset({ 
  views : {
    city : function(city) {
      return this.where({ city : city });
    }
  }
}

Also, add a way to tell the parent dataset to update its view. It should take in the params required by the view function.

ds.updateView('city', cityname);

Particularly relevant for products.