MLS Database Template

[angolden]

I am starting to work on a project for a friend who is a realtor here in Dallas. I don't like to reinvent the wheel if I don't have to and I haven't found great database models for a MLS database. We will be pulling the full IDX data feed from the NTREIS MLS (RapMLS). The RDBMS being used is MySQL but I can easily convert MSSQL, MySQL, Access, etc.

Anyone have a model they are willing to share? Thanks in advance!

[frobn]

I am starting to work on a project for a friend who is a realtor here in Dallas. I don't like to reinvent the wheel if I don't have to and I haven't found great database models for a MLS database. We will be pulling the full IDX data feed from the NTREIS MLS (RapMLS). The RDBMS being used is MySQL but I can easily convert MSSQL, MySQL, Access, etc.

Anyone have a model they are willing to share? Thanks in advance!

If you are going to do your own conversion take a look at http://open-realty.org. I would stay with mysql.

[langard]

MySQL, etc., is the database itself, not the Management System (RDBMS). If you have PHP installed, use PHPMyAdmin to manage your database. It is a powerful tool and you can import/export with ease.

[angolden]

MySQL, etc., is the database itself, not the Management System (RDBMS). If you have PHP installed, use PHPMyAdmin to manage your database. It is a powerful tool and you can import/export with ease.

Well, not to sound argumentative but since you

MySQL 5.0 may not meet all of Codd's 12 Rules in ideal fashion (Codd is the godfather of RDBMS theory so to speak) is not ANSI-92 compliant (let alone ANSI-99 or ANSI-2003) it is indeed an RDBMS and not a database. By definition a database (sometimes mistakenly referred to as a schema, which is the definition of the objects in a database such as tables, views, stored procedures, etc.), which is a collection of data. MySQL, Microsoft SQL, Oracle, IBM DB2, PostgreSQL Access, etc. are all RDBMS' implementing various levels of feature support.

PHPMyAdmin is a client tool in the Client-Server model that simplifies the tasks involved with any RDBMS system. It is excellent piece of software and I consider it a valuable tool when I am in a pinch or working away from my office. I prefer other tools when I am doing anything substantial with MySQL. I have yet to find the perfect tool that offers both speed and simplicity for the easy stuff and good modeling and handling of complex schemas without going overboard on features or sacrificing stability. I use Navicat for simple stuff and Embarcadero ER/Studio, which is I find to be overkill for the majority of projects I have worked on lately. MySQL Workbench is showing some promise but is to buggy to be dependable just yet IMHO.

But I digress...the pieces all fit together as follows:

PHPMyAdmin is a client tool providing an easy-to-use interface for the MySQL RDBMS server and in doing so, simplifies the process' of defining schema's and working with databases.

The sad thing is that in (hopefully) clarifying the conceptual differences in database, RDBMS’ and PHPMyAdmin I have proven that my original request is slightly incorrectly phrased as I was trying to avoid being overly technical. So for the sake of technical accuracy I will restate my original request with improved clarity…

Does anyone have a 3NF(third normal form) schema for a good property database that they are willing to share?


References
Wikipedia: Codd's 12 Rules

Wikipedia: Database entry

Wikipedia: Comparison of RDBMS features

[langard]

Sorry, everything's fourth abnormal around here. For those readers who don't know what RDBMS stands for, it's Real DataBase Management System.

So far as I know, in order to have a database management system you have to have a.....database to manage. If you rule out all the popular databases as simple, you must either work for Oracle or Delphi I presume.

Regardless, I'm just trying to give you a hand with your query. If you want something more sophisticated, just tell me what language you like it compiled in. I'm still a little confused about what you actually want. A hook?

[corodyne]

Hello there angolden!

I am about to start working on a 3NF using DDS from Chilisource. I'm in the same boat and will be importing data from two different MLS's for a client... going to make it a bear!

Anyway, I'll let you know if I find one or come up with a solution in the short-term.

good luck!

[frobn]

Hello there angolden!

I am about to start working on a 3NF using DDS from Chilisource. I'm in the same boat and will be importing data from two different MLS's for a client... going to make it a bear!

Anyway, I'll let you know if I find one or come up with a solution in the short-term.

good luck!

I am curious as to what you come with. Lack of normalization limits some of the current applications.

[corodyne]

frobn,

To be honest, I'm not familiar with any of the commercially available tools for MLS integration via IDX. I'm going to wing it and see where it comes out.

How much do the commercially available solutions cost (putting aside things like Mambo and the other open-source CMS solutions)?

Chris

[frobn]

frobn,

To be honest, I'm not familiar with any of the commercially available tools for MLS integration via IDX. I'm going to wing it and see where it comes out.

How much do the commercially available solutions cost (putting aside things like Mambo and the other open-source CMS solutions)?

Chris

My experience is mostly with open source because of dismal support experiences with commercial products. They often start out ok but sooner or later go into a downward spiral. I have used open-realty and with a few modifications gotten it to scale to over 50000 listings. The two limitations of OR, for me, are an unorthodox db table configuration and its monolitic nature. An associates uses 'Hot Properties' for small projects, which he gives a qualified ok. I believe it is under $100. The reason I am interested in what you are doing is that I am working on a new (unreleased) open source listing management program build specifically for IDX.

[php4ever]

Hey guys I saw this post and thought I'd drop in a few notes.

The notion that applications need to be normalized is only partially true. I say that because like Frobn is saying with Open-Realty it does not have a normalized DB and honestly doesnt need one if the Agent / Broker plans only to have a few thousand listings. Any good server (Not the $5 per month stuff either) can handle the DB requirements for a setup like that.

Many of the things you say about normalization are correct and it would be a dream to have an application that is both Normalized and well designed as a a clean listing CMS for Realtors. One company has such a tool but they are PERL based applications and not worthy of my suggestion because PERL is a technology best used for extraction, evaluation and conversion types of applications and not real estate ones.

If its of interest I've posted over in UtterAccess a question about normalization and they delivered a few links to me that help in planning a Database.

You can read about it here; Utter Access DB Normalization

I see that frobn mentions the open-source arena again which is cool. I'm a little more cautious with open-source then he but frobn is correct in the assumption that many commercial applications lack support and ease of customization. My favorite commercial application which is partially open-source is X-Cart and they stand out as the exception to the rule. If a guy were to consider IDX then nothing that I'm aware of commercial exists. I do have a few applications that a former programmer at FNIS developed for me that I've been using and of course Frobns code but I'd be impressed to see a commercial application as well.