Share this Project

2 Comments on “PivotApp: Metadata-Driven Data Retrieval In Action”

  1. This is something very cool which I have been envisioning to do for a quite while. This provides a rapid approach for data analysis and cleanup before ingestion. Would it be possible to integrate JSON forms into your architecture for describing & wrapping form rendering metadata based on the granularity with in a JSON collection that is directly related to the files being consumed? I want a model to be driven out of files metadata. For example, a file may have a long key such as Country, State, County, Gender, names & phone number. In this example, it might be possible to correlate country as a drop down whose selection drive another drop down to state, so on so forth and the details presented in a grid. This is one kind of metadata template but one should let the user choose the mapping based on the granularity disposition with in the collection. Also, I am not quite certain if DSL layer for business rules could be driven to attempt cross collection validation based on the metadata of relationships between collections. I hope I am not thinking too weird, some of it I did for a client and left to do other parts of the frame for a later date.

  2. Yes, I think that JSON Forms might be a better metadata DSL than the one I came up with. It’s usually better to ride a popular Open Source wave, since then the forms DSL should give us leverage across multiple problem domains. And as you point out, my DSL doesn’t handle compound keys or key dependencies.

    I haven’t tried to attack the cross-collection validation problem–however, I would look at leveraging joi browser to see how much mileage I could get out of it.

Leave a Reply

Your email address will not be published. Required fields are marked *