Hi Eric, The data module actually looks like exactly what I want. Thanks a lot for pointing this out. The "accessing of some data on my site which would guide it on how to interpret the data it reads" is basically what is defined here as a "Look-up table".
Thanks again! - paul r. On 2012-07-05, at 12:22 PM, Erik Alphenaar wrote: > Hi Paul, > > You're welcome! > > I was actually thinking you could store the data in a structured way in > content nodes in the datamodule, and not as "a file somewhere in the > hierarchy", for that would be a bit inflexible. > > Since you mentioned "reading data on several websites", I interpreted this in > the way that you need to read data from multiple sites, handle it in > different ways, and display it on your site. Meaning you have to structure > what data you want to show on your site, and map the remote content to that > format in an importer of some kind. If you have an automated way of loading > that content into your datamodule, you wouldn't need to modify anything in a > file, but just have the content in your repository. > > However, the sentence "I'd like to have my program access some data on my > site which would guide it on how to interpret the data it reads" threw me off > a bit. Could be sort of an importer, or could be something else... > Could you clarify with an example?? > > In the mean time. check out > http://documentation.magnolia-cms.com/modules/data.html#Importingdata to see > if this is a fitting solution for you. > > Best regards, > Erik Alphenaar. > > > On Thu, Jul 5, 2012 at 8:39 PM, Eagle Ravine <[email protected]> wrote: > Hi Eric, > > Thanks for the suggestion. It sounds like a great idea but it doesn't answer > my original question about where/how to store my data... Perhaps I should > clarify this a little - obviously I could store such data in a file somewhere > in the hierarchy. But I am planning to have my site webhosted, and am not > sure how easy it would be to just go in and update a file on a webhost > without uploading entirely new data for my website. Perhaps this is easier > than I think - and if so I'm sorry to bother everyone with "dumb questions". > I haven't had my own website in some time, and the last one I had was a very > simple one. > > Also sure, I'd love examples of doing this kind of thing if you have some > you'd like to point me to. > > Thanks, > > - paul r. > > On 2012-07-05, at 10:39 AM, Erik Alphenaar wrote: > > > Hi Paul, > > > > Why not schedule an importer and import the external data into a > > predefined format into the data module? This way the content is > > easily accessible, and does not rely on performance etc of the other > > sites. > > > > You could schedule the job to run daily or weekly or whatever using a > > cron / quartz trigger. > > > > Hope this suits your needs! Can point you to some nice examples. > > > > > > Best regards, > > Erik Alphenaar. > > www.orange11.nl > > > > On 5 jul. 2012, at 19:19, "Paul Rasmussen (via Magnolia Forums)" > > <[email protected]> wrote: > > > >> Hi, > >> > >> I'm planning to write some software to display some data on my site which > >> is not generally available but which can be gleaned from reading data on > >> several websites. To do this I'd like to have my program access some data > >> on my site which would guide it on how to interpret the data it reads. A > >> rough example is my data could say that the site "foo.edu" has data in > >> "format 1" and the site "bar.edu" has data in "format 2". I don't expect > >> this data to change often but sometimes it will need to be updated. I am > >> wondering if anyone has any suggestions about how this might best be > >> accomplished in terms of where best to store such data so that it can be > >> read programmatically and edited by me but not by anyone who accesses my > >> site. > >> > >> Thanks, > >> > >> - paul r. > >> > >> -- > >> Context is everything: > >> http://forum.magnolia-cms.com/forum/thread.html?threadId=3c905056-70fc-4d0d-a7f4-3544c668adb0 > >> > >> > >> ---------------------------------------------------------------- > >> For list details, see > >> http://www.magnolia-cms.com/community/mailing-lists.html > >> Alternatively, use our forums: http://forum.magnolia-cms.com/ > >> To unsubscribe, E-mail to: <[email protected]> > >> ---------------------------------------------------------------- > >> > > > > > > ---------------------------------------------------------------- > > For list details, see > > http://www.magnolia-cms.com/community/mailing-lists.html > > Alternatively, use our forums: http://forum.magnolia-cms.com/ > > To unsubscribe, E-mail to: <[email protected]> > > ---------------------------------------------------------------- > > > > > > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > > > ---------------------------------------------------------------- > For list details, see http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
