Re: Online magazine- monthly updates and such

This WebDNA talk-list message is from

1999


It keeps the original formatting.
numero = 22642
interpreted = N
texte = I thought about an issue number (which they've been doing for 5 years now- the digital issue will be #61) but issue numbers generally relate to an item that is issued on a specific regular basis- ie January 1999 issue of National Geographic. You can be assured that they will not come out with a January 15, 1999 because you paid for a 1 year subscription with an assumed delivery of 12 issues.I was thinking of a date-issue because the client can then update the db anytime they wish and the site will reflect that change (and their customers will know about it). If you want to see what I'm talking about, the site's at http://cat.pagehouseinc.com/airwaysnews_store/index.tpl (still in early 'beta', but you can log in as test username test for a cruise).I might go to issues, but the problem is that the clients' clients won't have a date associated with the info and won't have a relative gauge for the information's age. Due to the nature of the data (sort of a Airplane registration spotting affair) it is fairly date sensitive (not that I understand what it is or how someone will use it- but hey, what do I know?).The db file is only 40K (and will only probably grow to 1-2Mb) so hey, I'll add issues, why not?Thanks for the help.Bill>>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. > >>Now the question is, how would be the easiest way to organize it by month? >>This is the first non-store WebCat site i've done and it's actually a bit >>scary (no SKU or [cart] to deal with) > >I think it would be a good idea to build a field into the database that is >simply the issue number. > >Technical Support | ==== eCommerce and Beyond ==== >Pacific Coast Software | WebCatalog, WebMerchant, >11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, >San Diego, CA 92128 | Typhoon >619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ -- Bill Heissenbuttel PageHouse, Inc. bill@pagehouse.com Internet Presence Provider http://www.pagehouse.com (509) 892-1973 Associated Messages, from the most recent to the oldest:

    
  1. Re: Online magazine- monthly updates and such (Bill Heissenbuttel 1999)
  2. Re: Online magazine- monthly updates and such (Peter Ostry 1999)
  3. Re: Online magazine- monthly updates and such (PCS Technical Support 1999)
  4. Re: Online magazine- monthly updates and such (Martin Bech 1999)
  5. Online magazine- monthly updates and such (Bill Heissenbuttel 1999)
I thought about an issue number (which they've been doing for 5 years now- the digital issue will be #61) but issue numbers generally relate to an item that is issued on a specific regular basis- ie January 1999 issue of National Geographic. You can be assured that they will not come out with a January 15, 1999 because you paid for a 1 year subscription with an assumed delivery of 12 issues.I was thinking of a date-issue because the client can then update the db anytime they wish and the site will reflect that change (and their customers will know about it). If you want to see what I'm talking about, the site's at http://cat.pagehouseinc.com/airwaysnews_store/index.tpl (still in early 'beta', but you can log in as test username test for a cruise).I might go to issues, but the problem is that the clients' clients won't have a date associated with the info and won't have a relative gauge for the information's age. Due to the nature of the data (sort of a Airplane registration spotting affair) it is fairly date sensitive (not that I understand what it is or how someone will use it- but hey, what do I know?).The db file is only 40K (and will only probably grow to 1-2Mb) so hey, I'll add issues, why not?Thanks for the help.Bill>>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. > >>Now the question is, how would be the easiest way to organize it by month? >>This is the first non-store WebCat site i've done and it's actually a bit >>scary (no SKU or [cart] to deal with) > >I think it would be a good idea to build a field into the database that is >simply the issue number. > >Technical Support | ==== eCommerce and Beyond ==== >Pacific Coast Software | WebCatalog, WebMerchant, >11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, >San Diego, CA 92128 | Typhoon >619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ -- Bill Heissenbuttel PageHouse, Inc. bill@pagehouse.com Internet Presence Provider http://www.pagehouse.com (509) 892-1973 Bill Heissenbuttel

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:

[OT] DOD again (2003) Snake Bites (1997) RE: type 2 errors with ssl server (1997) 4.0 send email ticks. . (2000) Bill To - Ship To Information display (1997) [OT] Display Glitch (2004) Single Link browsing (1997) Locking up with WebCatalog... (1997) WebDNA handler in Httpd.conf being erased [fixed] (2005) WebCat2 Append problem (B14Macacgi) (1997) Just Testing (1997) SV: Mass Mail (2000) Cross OS Compatible HTML emailing (2003) Re:Change WebDNA-Talk Mail due to no digest for 1wk (1997) Email Set-Up? (1997) [WebDNA] OT - does anyone know how to get Fetch/BBedit to leave (2009) More than one db with the same namn (was: WC2f3) (1997) Remove from list server (1997) Attn: Bug in GeneralStore example b15 (1997) [shownext] and sort (1998)