importing and publishing static (x)html pages

Hi,

we try to get used with daisy and its concepts and have some questions.

We would like to have a scheduler, that from time to time imports some date
into the CMS.
Could that be done using the import function?

Additionally, we would like to export static (X)HTML onto a named drive.
This should also be triggered by a scheduler.
A static publishing function will be developed in the future, according to
daisy wiki. But maybe there is already a way to publish static html-pages
(without using wget or forrestbot).

Thanks for you help in advance!
Florian

--
View this message in context: http://www.nabble.com/importing-and...4p17750924.html
Sent from the Daisy - General mailing list archive at Nabble.com.

 ________________________________________
_______
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services...rt.html

mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Hi Florian,

Florian Rheindorf wrote:
> Hi,
>=20
> we try to get used with daisy and its concepts and have some questions.
>=20
> We would like to have a scheduler, that from time to time imports some =
date
> into the CMS. Could that be done using the import function?

I didn't understand what you would like to import, yet if you'd like to d=
isplay content from another web service, you could also fetch it with a D=
aisy/Cocoon extension, eventualy cleaning it and then transforming it wit=
h XSLT.

There may be many other ways to do what you want, this is just one I've b=
een trying with success, grabing content from XHTML pages and styling the=
m on the fly. If you'd like, I can provide you with some code to get you =
started.

> Additionally, we would like to export static (X)HTML onto a named drive=
.
> This should also be triggered by a scheduler.=20
> A static publishing function will be developed in the future, according=
to
> daisy wiki. But maybe there is already a way to publish static html-pag=
es
> (without using wget or forrestbot).

Here also, there are many solutions. I am currently doing this with an An=
t script, that grabs the content with 'wget', fixes the links and the pus=
hes the fixed content to another server via FTP. The Ant script is trigge=
red by the cron service on the server running the Daisy instances.

HTH, regards,

Olivier

--=20
Le Petit Atelier de G=E9nie logiciel
t. +41-21-6487665, m. +41-76-5166212, http://www.petit-atelier.ch/=20
 ________________________________________
_______
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/sup=
port.html
mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

On Tue, 2008-06-10 at 02:07 -0700, Florian Rheindorf wrote:
> Hi,
>
> we try to get used with daisy and its concepts and have some questions.
>
> We would like to have a scheduler, that from time to time imports some dat
e
> into the CMS.
> Could that be done using the import function?

The import tool can be used, but you would need to massage your data
into the format used by the import tool.

An alternative approach would be to use the API to create documents and
populate them.  This assumes the process responsible of creating the
documents knows how to obtain the data and store it in documents.

You should also have a look at the sync tool (in the source code under
applications/sync).

Both approaches have their value - much depends on specifics of your
situation. (Are you importing existing HTML pages? -> make sure they
still look ok after cleaning. How much data are you expecting
(#documents?, #bytes?).  Will the tool also be responsible of updating
data previously imported? ...)


>
> Additionally, we would like to export static (X)HTML onto a named drive.
> This should also be triggered by a scheduler.
> A static publishing function will be developed in the future, according to
> daisy wiki. But maybe there is already a way to publish static html-pages
> (without using wget or forrestbot).

I don't have experience with forrestbot, but from the short description
above, I would say wget is your friend.

>
> Thanks for you help in advance!
> Florian
>
 ________________________________________
_______
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services...rt.html

mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Thanks so far for the answers.

OK, lets get more specific.
I would like to do something like content syndication and therefore I'm
looking for an easy to use open source CMS.
We want to to create some basic importers, like html, xhtml, http, xml,
which read data from different sources and store the content as XML in a
repository (which could e.g. be daisy).
The content then gets enriched manuelly with some attributes and then it
should be automatically be exported into the file system in a different
format (mostly (x)html).
The content should be version controlled.

For performance reasons I would prefer that the content is directly
accessible through the file system.

Thanks for your support.
--
View this message in context: http://www.nabble.com/importing-and...4p17753867.html
Sent from the Daisy - General mailing list archive at Nabble.com.

 ________________________________________
_______
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services...rt.html

mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

On Tue, 2008-06-10 at 05:10 -0700, Florian Rheindorf wrote:
>
> Thanks so far for the answers.
>
> OK, lets get more specific.
> I would like to do something like content syndication and therefore I'm
> looking for an easy to use open source CMS.
> We want to to create some basic importers, like html, xhtml, http, xml,
> which read data from different sources and store the content as XML in a
> repository (which could e.g. be daisy).

As noted, make sure it is valid daisy html (anyway the htmlcleaner will
make sure it its) - otherwise use a document type like LiteralHtml,
which has its own drawbacks.

> The content then gets enriched manuelly with some attributes and then it
> should be automatically be exported into the file system in a different
> format (mostly (x)html).
> The content should be version controlled.
>
> For performance reasons I would prefer that the content is directly
> accessible through the file system.

I assume this is for the manual editing phase... Daisy does store its
contents on the filesystem, but it is not intended to be edited manually
whatsoever.  If you want to edit the data, you should use the wiki
interface or make your changes on an exported set
('export-edit-import'), or before importing the first time
('prepare-edit-import')

Lots of luck,
Karel

>
> Thanks for your support.
 ________________________________________
_______
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services...rt.html

mail to: daisy-81qHHgoATdGcMQoVcdA18UB+6BGkLq7r@public.gmane.org
list information: http://lists.cocoondev.org/mailman/listinfo/daisy