Currently, while creating a new dataset one adds the symbols manually and they remain there until modified (static method).
It would be nice if one could create a new WealthData (WD) permanent dataset from 2 (or more) WD datasets. The purpose of creating it this way (dynamic method) is that whenever there's a change in the parent datasets (additions, deletions, symbol changes, etc.) it would automatically get reflected in this dataset w/o the user having to manually modify the symbols.
Down the road I suppose this functionality could also be extended to other data providers, or even create a mix from diverse sources.
It would be nice if one could create a new WealthData (WD) permanent dataset from 2 (or more) WD datasets. The purpose of creating it this way (dynamic method) is that whenever there's a change in the parent datasets (additions, deletions, symbol changes, etc.) it would automatically get reflected in this dataset w/o the user having to manually modify the symbols.
Down the road I suppose this functionality could also be extended to other data providers, or even create a mix from diverse sources.
Rename
QUOTE:
it would automatically get reflected in this dataset w/o the user having to manually modify the symbols.
Nothing happens automatically. The WD built-in DataSets (Dow 30, DAX etc.) or some other (like the Fidelity Select Sector funds DataSet, for example) are powered by a DataSetProvider which either obtains the constituent history from the WD API or from a canned resource (the Fidelity funds DataSet). We do this symbol tracking for a sound purpose i.e. to maintain an index's composition.
Creating a custom DataSet from N WD DataSets (which follow the official indices per se, to stress it) while taking its history is an undeveloped idea. Just consider that a symbol can be (and frequently is) part of multiple WD DataSets (Nasdaq 100 and S&P 500, for instance).
Just as you have MetaStrategy which includes multiple strategies (but doesn't modify them) this type of dataset would be a MetaDataset.
Duplicate symbols would naturally be excluded, as happens currently (when one adds symbols from different indices).
Duplicate symbols would naturally be excluded, as happens currently (when one adds symbols from different indices).
It's not about "duplicate symbols". A symbol can be part of multiple indices at the same time and/or historically BUT its history of changes as a constituent could be taken from one roster. That's the inherent flaw of this gimmick.
And before you say "let me specify AAPL's membership manually at the time of DataSet creation: Nasdaq 100, Dow 30 or S&P 500" let me suggest you create your own DataSetProvider and maintain the history of components yourself.
https://www.wealth-lab.com/Support/ExtensionApi/DataSetProvider
And before you say "let me specify AAPL's membership manually at the time of DataSet creation: Nasdaq 100, Dow 30 or S&P 500" let me suggest you create your own DataSetProvider and maintain the history of components yourself.
https://www.wealth-lab.com/Support/ExtensionApi/DataSetProvider
We actually had as facility like this in WL6 called WatchLists, but Eugene brings up a good point about the complication of doing this with WL8's new dynamic DataSets.
The point wasn't to create a dataset on-the-fly but rather a permanent one that one can assign for Portfolio backtesting in individual strategies.
I was not talking about creating a DataSet on-the-fly, whatever it may mean.
Your Response
Post
Edit Post
Login is required