Re: Online magazine- monthly updates and such
This WebDNA talk-list message is from 1999
It keeps the original formatting.
numero = 22549
interpreted = N
texte = At 21:58 Uhr -0800 11.01.1999, Bill Heissenbuttel wrote:>I've got a magazine that will need monthly updates, generally once a month>(but may become bi-monthly). I'm thinking about putting all the info into>one db, with the different issue dates in the db.>>For example, The db will look like this:>>issue location airline AircraftType regn MSN update>02/01/1999 USA ABX Air 767-281 N775AX 22790/LN 90 bought from>...>>and the date will change (the next issue might be 03/01/1999).I am currently working on a website with three magazines (weekly andmonthly) and an admin interface for updates. The admin can collect as muchdata as he likes and when the day comes he just clicks on a button - thenew issue goes online and the old one goes into the archive. I have alldata in the database.If that is somehow similar to your project, my experiences might be helpful:Do not use dates only, number the issues. And use a field as a flag tomark the records as online or offline.Here are the most relevant fields of my database:Field Example Description of field------------------------------------------------------------------------db_ID 12345678 (the SKU)db_Medium aw (code for this magazine)db_Jahr 1999 (year)db_Ausgabe 13 (number of the issue)db_AusgabeID aw_1999_13 (unique code for one issue of one magazine, consists of db_Medium, db_Jahr and db_Ausgabe)db_Artikel 6 (number of one text-article in one issue)db_Status active (can have three states: new, active, old)The system is that I have a code for the specific magazine, a number forthe issue of this magazine and numbers for all text-articles within thismagazine. It is even easy to link an image to an article if you give it aname which fits into the system.The field db_Status is very important - you will actually have 3possibilities: a magazine can be online, old (maybe in the archive) and youneed a place where you can collect data BEFORE it goes online.If I put you an issue online, WebCat changes all active records to oldand all which belongs to the new issue to active.So the admin can work on a new magazine whenever he like and finally itgoes smooth online with a mouseclick... :-)Peter++++++++++++++++++++++++++++++++++++++++++++++++Peter Ostry - Vienna/Austria - www.ostry.comFon ++43-1-877 74 54 Fax ++43-1-877 74 54-21++++++++++++++++++++++++++++++++++++++++++++++++
Associated Messages, from the most recent to the oldest:
At 21:58 Uhr -0800 11.01.1999, Bill Heissenbuttel wrote:>I've got a magazine that will need monthly updates, generally once a month>(but may become bi-monthly). I'm thinking about putting all the info into>one db, with the different issue dates in the db.>>For example, The db will look like this:>>issue location airline AircraftType regn MSN update>02/01/1999 USA ABX Air 767-281 N775AX 22790/LN 90 bought from>...>>and the date will change (the next issue might be 03/01/1999).I am currently working on a website with three magazines (weekly andmonthly) and an admin interface for updates. The admin can collect as muchdata as he likes and when the day comes he just clicks on a button - thenew issue goes online and the old one goes into the archive. I have alldata in the database.If that is somehow similar to your project, my experiences might be helpful:Do not use dates only, number the issues. And use a field as a flag tomark the records as online or offline.Here are the most relevant fields of my database:Field Example Description of field------------------------------------------------------------------------db_ID 12345678 (the SKU)db_Medium aw (code for this magazine)db_Jahr 1999 (year)db_Ausgabe 13 (number of the issue)db_AusgabeID aw_1999_13 (unique code for one issue of one magazine, consists of db_Medium, db_Jahr and db_Ausgabe)db_Artikel 6 (number of one text-article in one issue)db_Status active (can have three states: new, active, old)The system is that I have a code for the specific magazine, a number forthe issue of this magazine and numbers for all text-articles within thismagazine. It is even easy to link an image to an article if you give it aname which fits into the system.The field db_Status is very important - you will actually have 3possibilities: a magazine can be online, old (maybe in the archive) and youneed a place where you can collect data BEFORE it goes online.If I put you an issue online, WebCat changes all active records to oldand all which belongs to the new issue to active.So the admin can work on a new magazine whenever he like and finally itgoes smooth online with a mouseclick... :-)Peter++++++++++++++++++++++++++++++++++++++++++++++++Peter Ostry - Vienna/Austria - www.ostry.comFon ++43-1-877 74 54 Fax ++43-1-877 74 54-21++++++++++++++++++++++++++++++++++++++++++++++++
Peter Ostry
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Running 2 two WebCatalog.acgi's (1996)
I forgot (1998)
Text data with spaces in them... (1997)
Shopping Cart - prices? (1997)
Tiny Store (1998)
WebCat2 - storing unformatted date data? (1997)
Java Path Follow Up (2004)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
Buying sans cart (1997)
Hiding Email Addresses (2003)
Sorting a [listdatabases] (2003)
Kaaaaahhhhhhhnnnnnnn! (1997)
RE: Help name our technology! (1997)
Credit Card Checking?? (1998)
[taxRate] [TaxTotal] ? (1997)
Still Stumped on ShowNext...HELP! (1997)
This message couldn't reach the list! (multi-column (1998)
Extended [ConvertChars] (1997)
WebCatalog for Postcards ? (1997)
Projects & Contractors (1997)