Text 3168, 80 rader
Skriven 2005-03-17 11:01:02 av Glenn Meadows (1:379/45)
     Kommentar till en text av Adam (1:379/45)
Ärende: Re: Programmers help needed.
====================================
From: "Glenn Meadows" <gmeadow@comcast.net>

Answers to questions:

1).  I'm double checking, but I think that 1 file per CD is required.  At one
point, Napster said just add to the bottom of the xl spread sheet.  I think all
would LIKE and XML form, but some accept an XL spreadsheet, grudgingly.

2).  Oh, anything.  We've got FileMaker Pro here, and there is the ubiquitous
Access.  Again, this is a TOOL we use to generate this data one time, since
once the product is on a service, it's unlikely we'll need to generate that
info for that service again.  It might be necessary if other services come
online (a likely scenario), so the ability to locally craft the style of output
needed for a new service would be a requirement.  So, essentially, we're
looking at a source database, and a report generator that allows us to pick the
data needed, and the order it's to be placed, and the format of the output of
that report.

--

Glenn M.
"Adam" <acompletemystery@somewhere.org> wrote in message
news:4239b210@w3.nls.net...
> Glenn Meadows wrote:
>
>> OK, let's start a discussion on how/what we need to accomplish what is
>> currently a very typing intensive task.  I need some input, and possible
>> costs and offers to create this "thing".
>>
>> When we provide content to the online services (music), each service
>> requires a slightly different set of information/detail down to the track
>> level of the CD.  This includes (but not specifically limited to), CD
>> name, UPC code, Artist name, Song titles, Song Writers, Song Publishers,
>> Year of release, ISRC code (special unique song identifier used for
>> reporting purposes), eligible countries of distribution, etc, etc.  Some
>> services require an XML document for each CD, some request an XL
>> spreadsheet is a specific format, which they then suck back into their
>> system.
>>
>> Right now, we service, oh, 20+ DIFFERENT services that sell music, and
>> the time required to fill out these forms in the specific formats takes
>> more time than I care to think.
>>
>> I'd like to discuss setting up a specific database that would be a super
>> set of ALL data required, and then being able to create and output
>> "report" for each service that created the specific style report/document
>> that each required for each title.  Thus, we'd enter the data ONE TIME,
>> and then just push buttons, run a script, etc, that would output the info
>> required.
>>
>> Who wants to start the discussion with idea on how this should be done?
>> Realize that we do NOT have the personnel on staff to create this item,
>> although portions of it MIGHT be in place and could be expanded upon, or
>> could be used to at least create the basic input to the new database,
>> where the only entry would be the missing information.
>>
>> Is any of that clear?
>>
>> I know Adam is heavy into various DB projects, using XML as part of the
>> results.
>>
>> Who wants to start the ball rolling please?
>>
> Quick question as I'm about to head home (but then I'll probably pick this
> up from home)
>
> A) Is this info required as 1 file per artist per service or 1 big file
> for all artists etc per service or what?
> B) Can the far end system deal with duplicates (i.e. you can simply kick
> out all info for all artists each time).
>
> Other than that, if XML....then it's easy & if xl then stick to CSV coz
> that's easy too.
>
> BTW what sort of db/appserv were you thinking of using?
>
> Adam

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)