Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Case: Structured View of Messy Data #49

Open
thorwhalen opened this issue Jan 30, 2020 · 0 comments
Open

Use Case: Structured View of Messy Data #49

thorwhalen opened this issue Jan 30, 2020 · 0 comments

Comments

@thorwhalen
Copy link
Member

A solution: Data separating malls, that is, a store of stores that offer the clean perspectives we need.

Example.

I've often been in the situation where a client presented me with a folder containing various types of datas that were necessary for a project. Often enough, the grouping of these types of data could be made on the basis of the paths only (subfolder names, extensions, filename patterns).

For this case there's some quite obvious solution:
(1) Write rules that group keys together or filter them out
(2) Map the groups to some store each with their own key and value handling
(3) Put it all together nicely to make general a mall that gives us the perspective we need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant