|
|
Posted by MassiveProng on 04/10/07 06:46
On Tue, 10 Apr 2007 02:05:28 -0400, "Doug MacLean"
<Webmaster@Hometheaterinfo.com> Gave us:
>"MassiveProng" <MassiveProng@thebarattheendoftheuniverse.org> wrote in
>message news:<538413hrafclasg30fs6itk36ptpk0jepp@4ax.com>...
>
>> On Tue, 3 Apr 2007 01:04:16 -0400, "Doug MacLean"
>
>> <Webmaster@Hometheaterinfo.com> Gave us:
>
>>
>
>> >"MassiveProng" <MassiveProng@thebarattheendoftheuniverse.org> wrote
>
>> >in
>
>> >message news:dloj03tn1ck8qm24kptij13jno1coqsme9@4ax.com...
>
>> >> On Tue, 27 Mar 2007 20:18:36 -0700, MassiveProng
>
>> >> <MassiveProng@thebarattheendoftheuniverse.org> Gave us:
>
>> >>
>
>> >>>Hey, does the main spreadsheet have the updates, or is that file
>
>> >>>needed as well?
>
>> >>>
>
>> >>>http://www.hometheaterinfo.com/dvdlist.htm
>
>> >>
>
>> >>
>
>> >> Hey doug, I noticed that you include disc type, ie HD or BluTurd in
>
>> >> the title in parenthesis.
>
>> >>
>
>> >> Why not add a column for media type?
>
>> >>
>
>> >> What happened to your logic, man!?
>
>> >
>
>> >The logic is there. Look in the column 'Verisions' and it lists if
>
>> >the DVD
>
>> >is UMD, HD-DVD, Blu-ray etc. The format is also listed in the title to be
>
>> >consistent with how the disc is named by the studio.
>
>> >
>
>> >Also, the main file always has the updates. If you download the main
>
>> >you are
>
>> >up to date.
>
>> >
>
>> >Doug MacLean
>
>> >http://www.hometheaterinfo.com
>
>> >
>
>>
>
>>
>
>> Also, on the spreadsheet, you could also "FREEZE" the top line, if
>
>> you know how to do that, so it doesn't scroll with the data, and a "Do
>
>> I Own It" column could be added so we can use the list as a database.
>
>>
>
>> Also, having the form factor column would facilitate sorting of the
>
>> list for users, as opposed to your keeping it in the title column
>
>> which does not support that form of sort at all.
>
>>
>
>> It wouldn't take much work to make the list far more useful.
>
>>
>
>> Great list, but it appears, a lazy attitude.
>
>>
>
>> I suppose ideally a separate list for LD, DVD, HD DVD, and BR would
>
>> be the correct way to do it.
>
>>
>
>> Oh and hey! That would also negate your non-existent copyright or
>
>> any claim thereto!
>
>>
>
>> Compiling a list of publicly available data makes the list a PD
>
>> item, regardless of your declared "rights". Let alone the fact that
>
>> you would have a really hard time taking to task anyone that made such
>
>> a list available in another form, or even a direct copy, for that
>
>> matter.
>
>>
>
>> Why even bother declaring it, since it wouldn't even hold up under
>
>> even the most conservative scruti
>
>Unfortunately, freezing the field names is not possible in SQL. I use SQL to
>create the various formats provided and it just sends out a plain XLS file.
>It also has the potential to interfer with import into some databases. A 'Do
>I Own' field is not really part of the schema of the data base since it does
>not relate to the actual data but a downstream client use. Since the data
>base is now too large for a single spreadsheet most people pull it into
>Access or some other data base program. I know form talking to some of them
>that they have a field for personal ownership on their end and import and
>merge the data into that table. Another way to handle it would be to use the
>unique identifier and use that to link a table of your personal collection
>with the data base. Just create a table with the Unique ID in it and only
>place entries in the table if you own it. I use something like this to track
>my own collection.
>
>Since we do not have access for a comprehensive list of LD we don't include
>them. Maintaining separate lists of all the new format variations would be
>very time intensive so we just include them as variation of DVDs. If you are
>using Excel you can turn on auto-filter and use the custom filter to isolate
>a give format. For example to find all HD-DVD just set versions to 'contains
>HD-DVD'. We are planning to include a format flag but that would change the
>schema and we do have some licensed clients that pull our files and we have
>to coordinate any change with them. It also will required some code changes
>in the procedures that process and export the tables. It's not difficult it
>just takes time to write and test and Michael and I both have real jobs that
>pay the bills that does cut into our development time for this. ;->
>
>As for the copyright it is not the data but the format and backend code that
>is covered. Sure anyone can get this data by culling through a bunch of
>sites but having it in the format provided is subject to copywrite. In this
>case it is the "form of material expression" that is subject to copywrite
>not the actual data. We have numerous vetting routines that have detected a
>lot of errors in the published particulars of some titles. Since we only ask
>for payment if another site is using the data base for profit there is
>really no problem. We have had a few times where sites were using out list
>for profit without even an acknowledgment and in each case the ISP of the
>site supported our request for the small payment and a link. A lot of hard
>work goes into this list and all we ask is a very minimal fee and a link
>back. Since this is not really a topic within the scope of this forum I
>would be glad to discuss this at any length you want. Just write me with a
>valid email address and we can go over any aspect of this you want.
>
>In any case thank you for your suggestions we will try to get the format
>field included as soon as possible.
>
>Doug MacLean
Thank you for the very informative, intelligent response.
Setting up a database would be a a pain in the ass for me, time wise,
but would seem to be better than going through the entire list with
search tools. Let the database do it!
Good call. I am sure there are some out there already set up too.
Perhaps I can find out, and you could add links to them in your page
that allow a person to grab both your list, and the DB app that allows
a more featured utilization thereof.
Again, thanks for the full featured response.
Navigation:
[Reply to this message]
|