#20 in Information management books
Use arrows to jump to the previous/next product

Reddit mentions of Data Model Patterns: A Metadata Map (The Morgan Kaufmann Series in Data Management Systems)

Sentiment score: 2
Reddit mentions: 2

We found 2 Reddit mentions of Data Model Patterns: A Metadata Map (The Morgan Kaufmann Series in Data Management Systems). Here are the top ones.

Data Model Patterns: A Metadata Map (The Morgan Kaufmann Series in Data Management Systems)
Buying options
View on Amazon.com
or
    Features:
  • Morgan Kaufmann Publishers
Specs:
Height9.36 Inches
Length7.61 Inches
Number of items1
Weight1.90038469844 Pounds
Width0.93 Inches

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Shuffle: random products popular on Reddit

Found 2 comments on Data Model Patterns: A Metadata Map (The Morgan Kaufmann Series in Data Management Systems):

u/SkyMarshal ยท 2 pointsr/Database

Sounds a bit presumptuous and close-minded of him, like he's got some 'best practice' design in mind and intends to fit it to your business (or your business to it).

Maybe that will work, but without any real due diligence he runs the risk of it not working, finding himself trying to jam a square peg into a round hole long after the peg has been constructed and paid for.

Which may be the way his consulting company works - use the same cookie-cutter approach that works for 80% of businesses, taking acceptable losses on the 20% where it fails. It just sucks for those 20%.

As for your question #1, the most thorough analysis and abstraction of an organization's processes, data, and metadata I have yet come across is detailed in the book Data Model Patterns: A Metadata Map.

It answers the question of how do you model an organization or system when the things being modeled don't all fit into conventional categories. Here's a paper on it I just found on Google too.

As for question #2, I assume he meant by 'plugging some tables into others' that it will be expandable to accommodate future needs, organizational/process changes, and upgrades. Theoretically, a normalized database that correctly specifies and implements all relations b/t in-scope data and metadata should allow exactly that - incorporation of new data or metadata as the business changes (leaving aside for now decisions about stored procs and business logic).

But the way you relate it, it sounds more like he's using that to justify using his canned solution and leaving you guys to complete it later when he's gone and $100k richer.

u/el_chief ยท 2 pointsr/Database

For your particular application I would look at OpenStreetMaps. Otherwise...

David Hay's