Nabble - Daisy - General

linking from books to documents ?

2009-11-27T00:50:07Z

Hello,

Is there a way to configure the PDF rendering of a book as such so
that daisy links in the book are transformed to a full URL, rather
than just daisy:123-ABC ? This has been mentioned a few times in the
past, has this been implemented for 2.1 ?

Thanks,
Jorg

[1] http://thread.gmane.org/gmane.comp.java.daisy.general/3983
[2] http://issues.cocoondev.org//browse/DSY-506
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

RE: Fulltext results options

2009-11-27T00:06:46Z

That’s it. I changed the code so it shows the first 40 characters of the summary in addition to the fulltext fragment. This will usually contain the document’s header.

Tx,

Mario.

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
Sent: donderdag 26 november 2009 21:06
To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Fulltext results options

Aah, now I see - I had to take a look at the source, see fulltext_searchresult.xsl in your daisy installation dir, line 107:

If there is a fulltext fragment to display, it will be displayed - in all other cases the summary is used.

So probably to revert to the desired behaviour, you should copy that stylesheet to your skin and change it so it always uses the summary.

HTH,

Karel

On Thu, Nov 26, 2009 at 5:30 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

Karel,

The query may have been the same, but it seems that previously the field summary was displayed. That contains the title (indeed, the first line of the document) which displays useful info about the document. Can we include that in the output?

Mario.

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
Sent: donderdag 26 november 2009 15:43

To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Fulltext results options

What do you mean by the 'main title of the document'? Do you mean the first <h1> element or whatever is in the top of the html content of the document?

I compared the query used for fulltext search against that from daisy 1.5, and it hasn't changed since then - it looks like this:

select name, summary, FullTextFragment(4), versionStateLastModified, Round(score * 100, 0) where FullText(....)

Perhaps your colleagues misremember seeing the document's name or the summary content in the search results.

Of course you can always use a custom search extension - you can make it show anything you want then. (It has been done before):

- make a copy of the existing FullTextSearchApple) and fulltext search results stylesheet

- set up your extension (create a sitemap etc)

- In layout.xsl, replace the url for the search form with your extension's url

- once you have the basics working, you can change the query (in the apple) and the stylesheet.

Regards,

Karel

On Thu, Nov 26, 2009 at 3:07 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

I’m talking about the default search page.

Currently you get the name of the document and part of the text. We would like to see the main title of the document, or a custom field in the results.

Some of my colleagues pointed out that in our previous version (1.5) either title or custom field were available in the results. Unfortunately I can’t check this anymore since we have only version 2.2 installed. Could this be correct?

Mario.

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
Sent: donderdag 26 november 2009 12:57
To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Fulltext results options

I don't think I fully understand your question. Are you talking about the default fulltext search page

(at http://server/.../site/search) or about queries contained in documents?

The document name is already shown in the fulltext search results (e.g. http://daisycms.org/daisy/search?query=daisy)

In documents, just use 'name' in the select clause. See the query language documentation ([0]) about 'FullText' and 'FullTextFragment'

Custom fields are referred to using #field. On the builtin search result page you can't get them because the select clause is fixed.

For queries in documents, just select #field.

[0] http://daisycms.org/daisydocs-2_3/373-cd/9-cd.html

HTH,

Karel

On Thu, Nov 26, 2009 at 12:19 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

We would like to include the documents title(s) in the fulltext search results. Where does this have to be defined?

Optionally we would like to include custom fields in the result page.

Tx,

Error! Filename not specified.

Mario Brackeva

Change & Monitoring Manager

T +32 2 454 27 79 • F +32 2 452 24 11

M +32 473 61 51 09

mario.brackeva@...

Brusselsesteenweg 347 • 1730 ASSE • persgroep.be

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: Fulltext results options

2009-11-26T12:06:26Z

Aah, now I see - I had to take a look at the source, see fulltext_searchresult.xsl in your daisy installation dir, line 107:

If there is a fulltext fragment to display, it will be displayed - in all other cases the summary is used.

So probably to revert to the desired behaviour, you should copy that stylesheet to your skin and change it so it always uses the summary.

HTH,

Karel

On Thu, Nov 26, 2009 at 5:30 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

Karel,

The query may have been the same, but it seems that previously the field summary was displayed. That contains the title (indeed, the first line of the document) which displays useful info about the document. Can we include that in the output?

Mario.

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
Sent: donderdag 26 november 2009 15:43

To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Fulltext results options

What do you mean by the 'main title of the document'? Do you mean the first <h1> element or whatever is in the top of the html content of the document?

I compared the query used for fulltext search against that from daisy 1.5, and it hasn't changed since then - it looks like this:

select name, summary, FullTextFragment(4), versionStateLastModified, Round(score * 100, 0) where FullText(....)

Perhaps your colleagues misremember seeing the document's name or the summary content in the search results.

Of course you can always use a custom search extension - you can make it show anything you want then. (It has been done before):

- make a copy of the existing FullTextSearchApple) and fulltext search results stylesheet

- set up your extension (create a sitemap etc)

- In layout.xsl, replace the url for the search form with your extension's url

- once you have the basics working, you can change the query (in the apple) and the stylesheet.

Regards,

Karel

On Thu, Nov 26, 2009 at 3:07 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

I’m talking about the default search page.

Currently you get the name of the document and part of the text. We would like to see the main title of the document, or a custom field in the results.

Some of my colleagues pointed out that in our previous version (1.5) either title or custom field were available in the results. Unfortunately I can’t check this anymore since we have only version 2.2 installed. Could this be correct?

Mario.

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
Sent: donderdag 26 november 2009 12:57
To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Fulltext results options

I don't think I fully understand your question. Are you talking about the default fulltext search page

(at http://server/.../site/search) or about queries contained in documents?

The document name is already shown in the fulltext search results (e.g. http://daisycms.org/daisy/search?query=daisy)

In documents, just use 'name' in the select clause. See the query language documentation ([0]) about 'FullText' and 'FullTextFragment'

Custom fields are referred to using #field. On the builtin search result page you can't get them because the select clause is fixed.

For queries in documents, just select #field.

[0] http://daisycms.org/daisydocs-2_3/373-cd/9-cd.html

HTH,

Karel

On Thu, Nov 26, 2009 at 12:19 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

We would like to include the documents title(s) in the fulltext search results. Where does this have to be defined?

Optionally we would like to include custom fields in the result page.

Tx,

Mario Brackeva

Change & Monitoring Manager

T +32 2 454 27 79 • F +32 2 452 24 11

M +32 473 61 51 09

mario.brackeva@...

Brusselsesteenweg 347 • 1730 ASSE • persgroep.be

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

RE: Fulltext results options

2009-11-26T08:30:31Z

Karel,

Mario.

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
Sent: donderdag 26 november 2009 15:43
To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Fulltext results options

What do you mean by the 'main title of the document'? Do you mean the first <h1> element or whatever is in the top of the html content of the document?

I compared the query used for fulltext search against that from daisy 1.5, and it hasn't changed since then - it looks like this:

select name, summary, FullTextFragment(4), versionStateLastModified, Round(score * 100, 0) where FullText(....)

Perhaps your colleagues misremember seeing the document's name or the summary content in the search results.

Of course you can always use a custom search extension - you can make it show anything you want then. (It has been done before):

- make a copy of the existing FullTextSearchApple) and fulltext search results stylesheet

- set up your extension (create a sitemap etc)

- In layout.xsl, replace the url for the search form with your extension's url

- once you have the basics working, you can change the query (in the apple) and the stylesheet.

Regards,

Karel

On Thu, Nov 26, 2009 at 3:07 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

I’m talking about the default search page.

Currently you get the name of the document and part of the text. We would like to see the main title of the document, or a custom field in the results.

Mario.

I don't think I fully understand your question. Are you talking about the default fulltext search page

(at http://server/.../site/search) or about queries contained in documents?

The document name is already shown in the fulltext search results (e.g. http://daisycms.org/daisy/search?query=daisy)

In documents, just use 'name' in the select clause. See the query language documentation ([0]) about 'FullText' and 'FullTextFragment'

Custom fields are referred to using #field. On the builtin search result page you can't get them because the select clause is fixed.

For queries in documents, just select #field.

[0] http://daisycms.org/daisydocs-2_3/373-cd/9-cd.html

HTH,

Karel

On Thu, Nov 26, 2009 at 12:19 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

We would like to include the documents title(s) in the fulltext search results. Where does this have to be defined?

Optionally we would like to include custom fields in the result page.

Tx,

Mario Brackeva

Change & Monitoring Manager

T +32 2 454 27 79 • F +32 2 452 24 11

M +32 473 61 51 09

mario.brackeva@...

Brusselsesteenweg 347 • 1730 ASSE • persgroep.be

Re: Fulltext results options

2009-11-26T06:43:01Z

What do you mean by the 'main title of the document'? Do you mean the first <h1> element or whatever is in the top of the html content of the document?

I compared the query used for fulltext search against that from daisy 1.5, and it hasn't changed since then - it looks like this:

select name, summary, FullTextFragment(4), versionStateLastModified, Round(score * 100, 0) where FullText(....)

Perhaps your colleagues misremember seeing the document's name or the summary content in the search results.

Of course you can always use a custom search extension - you can make it show anything you want then. (It has been done before):

- make a copy of the existing FullTextSearchApple) and fulltext search results stylesheet

- set up your extension (create a sitemap etc)

- In layout.xsl, replace the url for the search form with your extension's url

- once you have the basics working, you can change the query (in the apple) and the stylesheet.

Regards,

Karel

On Thu, Nov 26, 2009 at 3:07 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

I’m talking about the default search page.

Currently you get the name of the document and part of the text. We would like to see the main title of the document, or a custom field in the results.

Some of my colleagues pointed out that in our previous version (1.5) either title or custom field were available in the results. Unfortunately I can’t check this anymore since we have only version 2.2 installed. Could this be correct?

Mario.

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
Sent: donderdag 26 november 2009 12:57
To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Fulltext results options

I don't think I fully understand your question. Are you talking about the default fulltext search page

(at http://server/.../site/search) or about queries contained in documents?

The document name is already shown in the fulltext search results (e.g. http://daisycms.org/daisy/search?query=daisy)

In documents, just use 'name' in the select clause. See the query language documentation ([0]) about 'FullText' and 'FullTextFragment'

Custom fields are referred to using #field. On the builtin search result page you can't get them because the select clause is fixed.

For queries in documents, just select #field.

[0] http://daisycms.org/daisydocs-2_3/373-cd/9-cd.html

HTH,

Karel

On Thu, Nov 26, 2009 at 12:19 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

We would like to include the documents title(s) in the fulltext search results. Where does this have to be defined?

Optionally we would like to include custom fields in the result page.

Tx,

Mario Brackeva

Change & Monitoring Manager

T +32 2 454 27 79 • F +32 2 452 24 11

M +32 473 61 51 09

mario.brackeva@...

Brusselsesteenweg 347 • 1730 ASSE • persgroep.be

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

RE: Fulltext results options

2009-11-26T06:07:02Z

I’m talking about the default search page.

Currently you get the name of the document and part of the text. We would like to see the main title of the document, or a custom field in the results.

Mario.

I don't think I fully understand your question. Are you talking about the default fulltext search page

(at http://server/.../site/search) or about queries contained in documents?

The document name is already shown in the fulltext search results (e.g. http://daisycms.org/daisy/search?query=daisy)

In documents, just use 'name' in the select clause. See the query language documentation ([0]) about 'FullText' and 'FullTextFragment'

Custom fields are referred to using #field. On the builtin search result page you can't get them because the select clause is fixed.

For queries in documents, just select #field.

[0] http://daisycms.org/daisydocs-2_3/373-cd/9-cd.html

HTH,

Karel

On Thu, Nov 26, 2009 at 12:19 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

We would like to include the documents title(s) in the fulltext search results. Where does this have to be defined?

Optionally we would like to include custom fields in the result page.

Tx,

Mario Brackeva

Change & Monitoring Manager

T +32 2 454 27 79 • F +32 2 452 24 11

M +32 473 61 51 09

mario.brackeva@...

Brusselsesteenweg 347 • 1730 ASSE • persgroep.be

Re: Fulltext results options

2009-11-26T03:57:13Z

I don't think I fully understand your question. Are you talking about the default fulltext search page

(at http://server/.../site/search) or about queries contained in documents?

The document name is already shown in the fulltext search results (e.g. http://daisycms.org/daisy/search?query=daisy)

In documents, just use 'name' in the select clause. See the query language documentation ([0]) about 'FullText' and 'FullTextFragment'

Custom fields are referred to using #field. On the builtin search result page you can't get them because the select clause is fixed.

For queries in documents, just select #field.

[0] http://daisycms.org/daisydocs-2_3/373-cd/9-cd.html

HTH,

Karel

On Thu, Nov 26, 2009 at 12:19 PM, Mario Brackeva <Mario.Brackeva@...> wrote:

We would like to include the documents title(s) in the fulltext search results. Where does this have to be defined?

Optionally we would like to include custom fields in the result page.

Tx,

Mario Brackeva

Change & Monitoring Manager

T +32 2 454 27 79 • F +32 2 452 24 11

M +32 473 61 51 09

mario.brackeva@...

Brusselsesteenweg 347 • 1730 ASSE • persgroep.be

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Fulltext results options

2009-11-26T03:19:35Z

We would like to include the documents title(s) in the fulltext search results. Where does this have to be defined?

Optionally we would like to include custom fields in the result page.

Tx,

Mario Brackeva

Change & Monitoring Manager

T +32 2 454 27 79 • F +32 2 452 24 11

M +32 473 61 51 09

mario.brackeva@...

Brusselsesteenweg 347 • 1730 ASSE • persgroep.be

Re: Point in time

2009-11-25T06:16:46Z

Sorry, lost track of it, but I doubt that anyone has already done such a thing.

If you want to keep using the FullText expression in the query
language you can't just
implement it as a repository extension, so the most likely solution
would involve changes to the fulltext indexer and to the query
language.

Good luck,
Karel

2009/11/25 Aurélien Pelletier <aurelien.pelletier@...>:

> up
>
> 2009/11/12 Aurélien Pelletier <aurelien.pelletier@...>:
>> Hello,
>>
>> I'm evaluating Daisy CMS for a project to manage a documentation on
>> legal content.
>> One of my requirements is be to be able to do a point in time search
>> (search content by date).
>>
>> Currently Daisy only index the live version of a document and it is
>> impossible to do this point in time search.
>> I'm wondering how hard it would be to add this to daisy?
>>
>> My plan would be to:
>> - add a start and end publication date to every version of each document
>> - the end publication date would be the start publication date of the
>> next version (to avoid gap in time)
>> - add to the lucene index these start and end publication date
>> - index not only the live version but every published version
>> - modify the search to be able to search by date using the lucene index
>>
>> At this point the only issue I see is the growth of the lucene index
>> (but it is a simple matter of correct sizing)
>>
>> Anyone worked on this feature before? Anyone else interested, would it
>> be a valuable addition to Daisy?
>>
>> Thanks
>>
>> Aurélien Pelletier
>>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>

Point in time

2009-11-25T05:39:12Z

up

2009/11/12 Aurélien Pelletier <aurelien.pelletier@...>:

> Hello,
>
> I'm evaluating Daisy CMS for a project to manage a documentation on
> legal content.
> One of my requirements is be to be able to do a point in time search
> (search content by date).
>
> Currently Daisy only index the live version of a document and it is
> impossible to do this point in time search.
> I'm wondering how hard it would be to add this to daisy?
>
> My plan would be to:
> - add a start and end publication date to every version of each document
> - the end publication date would be the start publication date of the
> next version (to avoid gap in time)
> - add to the lucene index these start and end publication date
> - index not only the live version but every published version
> - modify the search to be able to search by date using the lucene index
>
> At this point the only issue I see is the growth of the lucene index
> (but it is a simple matter of correct sizing)
>
> Anyone worked on this feature before? Anyone else interested, would it
> be a valuable addition to Daisy?
>
> Thanks
>
> Aurélien Pelletier
>

[JIRA] Commented: (DSY-362) Inconsistent handling of case-sensitivity in document/part/field type names (and probably others)

2009-11-25T04:48:22Z

[ http://issues.cocoondev.org//browse/DSY-362?page=comments#action_13847 ]

Karel Vervaeke commented on DSY-362:
------------------------------------

Same problem for user names. (userManager.getUser(login) is case insensitive, but authentication requires the proper casing for user names).

Workaround to change the case of a part/field (useful only in some cases): E.g. to change $myfield to $MyField, rename $myfield to $myfield_old, add $MyField, use a document task to copy the contents of $myfield_old to $MyField.

> Inconsistent handling of case-sensitivity in document/part/field type names (and probably others)
> -------------------------------------------------------------------------------------------------
>
> Key: DSY-362
> URL: http://issues.cocoondev.org//browse/DSY-362
> Project: Daisy
> Type: Bug
> Components: Repository - database support
> Reporter: Bruno Dumon
> Priority: Minor
> Fix For: 2.4

>
> SQL searches in MySQL are case insensitive, though the names of document/part/field types in Daisy are case-sensitive. Currently it is possible to retrieve e.g. a document type by name even if the casing is not correct, though this does not work when the document type is retrieved from the cache. We need some consequent handling here, also taking care of the fact that other databases are case sensitive.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: Is there any class implements TextExtractor or TextExtractorManager?

2009-11-23T02:37:40Z

The implementations are called PDFTextExtractor, PlainTextExtractor, ...

AFAICS you can just instantiate them and call 'getText(InputStream is)'.

A better way to get the text is probably to get a hold of the TextExtractorManager (whichbasically contains a registry with all the mimetype -> extractor mappings). It's your lucky day, because the TextExtractorManager is exported in the spring configuration,

so you can get a hold of it if you put this in a spring container:

<daisy:import-service id="textExtractorManager" service="org.outerj.daisy.textextraction.TextExtractorManager"/>

HTH,

Karel

2009/11/23 迪陈 <chendi717@...>

How to get text of file(PDF,word,excel...) by daisy programming interface?

好玩贺卡等你发，邮箱贺卡全新上线！
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Is there any class implements TextExtractor or TextExtractorManager?

2009-11-23T00:16:46Z

How to get text of file(PDF,word,excel...) by daisy programming interface?

好玩贺卡等你发，邮箱贺卡全新上线！
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Matthew Barbarello is out of the office.

2009-11-19T05:01:42Z

I will be out of the office starting 11/19/2009 and will not return until
11/23/2009.

I will respond to your message when I return.

If this has to do with a Technical Publications issue, please contact
Thomas Connally.

For questions or comments on requirements templates, please contact Dhruv
Gupta and James Chan.

Thank you.

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: Large Attachments

2009-11-19T02:43:25Z

I wouldn't be surprise if Windows SMALL BUSINESS SYSTEM limits bandwith available...

http://www.experts-exchange.com/Networking/Windows_Networking/Q_24124300.html

Aurélien

On Thu, Nov 19, 2009 at 9:20 AM, Scott Warren <scottwarren@...> wrote:

Karel,

Thanks for the response. I am assured by the network administrators that the network is all ok and it's just the software. I tried putting Lighttp working as Reverse Proxy in front and it made no difference.

Daisy is installed in Jetty 6.1.22.

Does anyone know of any defaults (I can't see anything) that could be changed to increase the bandwidth in Jetty?

Regards

Scott Warren

Ocom Software - Quality Custom Software

On Thu, Nov 19, 2009 at 19:09, Karel Vervaeke <karel@...> wrote:
If the download via localhost works at regular speed, the problem is
probably with your network.

Possible things to test/use/check:
- Start by measuring the maximum communication speed between the
server and the client (use some network performance tests/benchmarks)
- chances are that it will turn out to be 2 mbps...
- Talk to your network administrators, they're likely to be able to
tell your more.
- If Daisy is deployed on Tomcat or behind an Apache reverse proxy,
check their settings (Although I would be surprised - I don't think
they are limited by default and you wouldn't have to ask if you had
set them yourself)
- On the server, look for firewall settings, possibly also at the
Windows license (I guess if the number of simultaneous client
connections can be limited by the license, perhaps the networking
speed can also limited?)

HTH,
Karel

On Thu, Nov 19, 2009 at 6:22 AM, scottwarren <scottwarren@...> wrote:
>
> I am having an issue with Daisy 2.3 on a Windows SBS Server (2003 I think).
>
> When the Users try and Download a Large PDF (In an Attachment Part) it seems
> to limit the download to 2mb/s. I have tried upgrading Jetty (in the hope
> that there may be a bug) to 6.1.22 and this has not fixed the issue.
>
> When I browse the page using localhost the file downloads in seconds.
>
> Thanks in advance for your reply.
>
> Scott Warren
> --
> View this message in context: http://old.nabble.com/Large-Attachments-tp26420587p26420587.html
> Sent from the Daisy - General mailing list archive at Nabble.com.
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: Large Attachments

2009-11-19T01:37:38Z

Great Idea, I will try it tomorrow (its late here in Australia)

Thanks for the suggestions.

Regards

Scott Warren

Ocom Software - Quality Custom Software

On Thu, Nov 19, 2009 at 19:28, Karel Vervaeke <karel@...> wrote:

If you already have lighttpd in front, try testing the download speed
by putting a large document under its document root
and try to download that from the client. If the speed significantly
over 2 Mbps?

(Just to be sure: lighttpd is running on the same server as Daisy , right?)

Karel

On Thu, Nov 19, 2009 at 9:20 AM, Scott Warren <scottwarren@...> wrote:
> Karel,
> Thanks for the response. I am assured by the network administrators that the
> network is all ok and it's just the software. I tried putting Lighttp
> working as Reverse Proxy in front and it made no difference.
> Daisy is installed in Jetty 6.1.22.
> Does anyone know of any defaults (I can't see anything) that could be
> changed to increase the bandwidth in Jetty?
>
> Regards
>
> Scott Warren
>
> Ocom Software - Quality Custom Software
>
>
>
> On Thu, Nov 19, 2009 at 19:09, Karel Vervaeke <karel@...>
> wrote:
>>
>> If the download via localhost works at regular speed, the problem is
>> probably with your network.
>>
>> Possible things to test/use/check:
>> - Start by measuring the maximum communication speed between the
>> server and the client (use some network performance tests/benchmarks)
>> - chances are that it will turn out to be 2 mbps...
>> - Talk to your network administrators, they're likely to be able to
>> tell your more.
>> - If Daisy is deployed on Tomcat or behind an Apache reverse proxy,
>> check their settings (Although I would be surprised - I don't think
>> they are limited by default and you wouldn't have to ask if you had
>> set them yourself)
>> - On the server, look for firewall settings, possibly also at the
>> Windows license (I guess if the number of simultaneous client
>> connections can be limited by the license, perhaps the networking
>> speed can also limited?)
>>
>> HTH,
>> Karel
>>
>>
>> On Thu, Nov 19, 2009 at 6:22 AM, scottwarren <scottwarren@...>
>> wrote:
>> >
>> > I am having an issue with Daisy 2.3 on a Windows SBS Server (2003 I
>> > think).
>> >
>> > When the Users try and Download a Large PDF (In an Attachment Part) it
>> > seems
>> > to limit the download to 2mb/s. I have tried upgrading Jetty (in the
>> > hope
>> > that there may be a bug) to 6.1.22 and this has not fixed the issue.
>> >
>> > When I browse the page using localhost the file downloads in seconds.
>> >
>> > Thanks in advance for your reply.
>> >
>> > Scott Warren
>> > --
>> > View this message in context:
>> > http://old.nabble.com/Large-Attachments-tp26420587p26420587.html
>> > Sent from the Daisy - General mailing list archive at Nabble.com.
>> >
>> > _______________________________________________
>> > daisy community mailing list
>> > Professional Daisy support:
>> > http://outerthought.org/en/services/daisy/support.html
>> > mail to: daisy@...
>> > list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>> >
>> _______________________________________________
>> daisy community mailing list
>> Professional Daisy support:
>> http://outerthought.org/en/services/daisy/support.html
>> mail to: daisy@...
>> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: Large Attachments

2009-11-19T00:28:49Z

If you already have lighttpd in front, try testing the download speed
by putting a large document under its document root
and try to download that from the client. If the speed significantly
over 2 Mbps?

(Just to be sure: lighttpd is running on the same server as Daisy , right?)

Karel

On Thu, Nov 19, 2009 at 9:20 AM, Scott Warren <scottwarren@...> wrote:

> Karel,
> Thanks for the response. I am assured by the network administrators that the
> network is all ok and it's just the software. I tried putting Lighttp
> working as Reverse Proxy in front and it made no difference.
> Daisy is installed in Jetty 6.1.22.
> Does anyone know of any defaults (I can't see anything) that could be
> changed to increase the bandwidth in Jetty?
>
> Regards
>
> Scott Warren
>
> Ocom Software - Quality Custom Software
>
>
>
> On Thu, Nov 19, 2009 at 19:09, Karel Vervaeke <karel@...>
> wrote:
>>
>> If the download via localhost works at regular speed, the problem is
>> probably with your network.
>>
>> Possible things to test/use/check:
>> - Start by measuring the maximum communication speed between the
>> server and the client (use some network performance tests/benchmarks)
>> - chances are that it will turn out to be 2 mbps...
>> - Talk to your network administrators, they're likely to be able to
>> tell your more.
>> - If Daisy is deployed on Tomcat or behind an Apache reverse proxy,
>> check their settings (Although I would be surprised - I don't think
>> they are limited by default and you wouldn't have to ask if you had
>> set them yourself)
>> - On the server, look for firewall settings, possibly also at the
>> Windows license (I guess if the number of simultaneous client
>> connections can be limited by the license, perhaps the networking
>> speed can also limited?)
>>
>> HTH,
>> Karel
>>
>>
>> On Thu, Nov 19, 2009 at 6:22 AM, scottwarren <scottwarren@...>
>> wrote:
>> >
>> > I am having an issue with Daisy 2.3 on a Windows SBS Server (2003 I
>> > think).
>> >
>> > When the Users try and Download a Large PDF (In an Attachment Part) it
>> > seems
>> > to limit the download to 2mb/s. I have tried upgrading Jetty (in the
>> > hope
>> > that there may be a bug) to 6.1.22 and this has not fixed the issue.
>> >
>> > When I browse the page using localhost the file downloads in seconds.
>> >
>> > Thanks in advance for your reply.
>> >
>> > Scott Warren
>> > --
>> > View this message in context:
>> > http://old.nabble.com/Large-Attachments-tp26420587p26420587.html
>> > Sent from the Daisy - General mailing list archive at Nabble.com.
>> >
>> > _______________________________________________
>> > daisy community mailing list
>> > Professional Daisy support:
>> > http://outerthought.org/en/services/daisy/support.html
>> > mail to: daisy@...
>> > list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>> >
>> _______________________________________________
>> daisy community mailing list
>> Professional Daisy support:
>> http://outerthought.org/en/services/daisy/support.html
>> mail to: daisy@...
>> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>

Re: Large Attachments

2009-11-19T00:20:38Z

Karel,

Thanks for the response. I am assured by the network administrators that the network is all ok and it's just the software. I tried putting Lighttp working as Reverse Proxy in front and it made no difference.

Daisy is installed in Jetty 6.1.22.

Does anyone know of any defaults (I can't see anything) that could be changed to increase the bandwidth in Jetty?

Regards

Scott Warren

Ocom Software - Quality Custom Software

On Thu, Nov 19, 2009 at 19:09, Karel Vervaeke <karel@...> wrote:

If the download via localhost works at regular speed, the problem is
probably with your network.

Possible things to test/use/check:
- Start by measuring the maximum communication speed between the
server and the client (use some network performance tests/benchmarks)
- chances are that it will turn out to be 2 mbps...
- Talk to your network administrators, they're likely to be able to
tell your more.
- If Daisy is deployed on Tomcat or behind an Apache reverse proxy,
check their settings (Although I would be surprised - I don't think
they are limited by default and you wouldn't have to ask if you had
set them yourself)
- On the server, look for firewall settings, possibly also at the
Windows license (I guess if the number of simultaneous client
connections can be limited by the license, perhaps the networking
speed can also limited?)

HTH,
Karel

On Thu, Nov 19, 2009 at 6:22 AM, scottwarren <scottwarren@...> wrote:
>
> I am having an issue with Daisy 2.3 on a Windows SBS Server (2003 I think).
>
> When the Users try and Download a Large PDF (In an Attachment Part) it seems
> to limit the download to 2mb/s. I have tried upgrading Jetty (in the hope
> that there may be a bug) to 6.1.22 and this has not fixed the issue.
>
> When I browse the page using localhost the file downloads in seconds.
>
> Thanks in advance for your reply.
>
> Scott Warren
> --
> View this message in context: http://old.nabble.com/Large-Attachments-tp26420587p26420587.html
> Sent from the Daisy - General mailing list archive at Nabble.com.
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: Large Attachments

2009-11-19T00:09:30Z

If the download via localhost works at regular speed, the problem is
probably with your network.

Possible things to test/use/check:
- Start by measuring the maximum communication speed between the
server and the client (use some network performance tests/benchmarks)
- chances are that it will turn out to be 2 mbps...
- Talk to your network administrators, they're likely to be able to
tell your more.
- If Daisy is deployed on Tomcat or behind an Apache reverse proxy,
check their settings (Although I would be surprised - I don't think
they are limited by default and you wouldn't have to ask if you had
set them yourself)
- On the server, look for firewall settings, possibly also at the
Windows license (I guess if the number of simultaneous client
connections can be limited by the license, perhaps the networking
speed can also limited?)

HTH,
Karel

On Thu, Nov 19, 2009 at 6:22 AM, scottwarren <scottwarren@...> wrote:

>
> I am having an issue with Daisy 2.3 on a Windows SBS Server (2003 I think).
>
> When the Users try and Download a Large PDF (In an Attachment Part) it seems
> to limit the download to 2mb/s. I have tried upgrading Jetty (in the hope
> that there may be a bug) to 6.1.22 and this has not fixed the issue.
>
> When I browse the page using localhost the file downloads in seconds.
>
> Thanks in advance for your reply.
>
> Scott Warren
> --
> View this message in context: http://old.nabble.com/Large-Attachments-tp26420587p26420587.html
> Sent from the Daisy - General mailing list archive at Nabble.com.
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>

Large Attachments

2009-11-18T21:22:58Z

I am having an issue with Daisy 2.3 on a Windows SBS Server (2003 I think).

When the Users try and Download a Large PDF (In an Attachment Part) it seems to limit the download to 2mb/s. I have tried upgrading Jetty (in the hope that there may be a bug) to 6.1.22 and this has not fixed the issue.

When I browse the page using localhost the file downloads in seconds.

Thanks in advance for your reply.

Scott Warren

Re: Re: daisy Digest, Vol 62, Issue 4

2009-11-17T23:59:20Z

Ah, you mean the parteditor applet - no, there doesn't appear to be
much information about it (not that I can find back anyway).

There is a screencast which demonstrates it fairly well. It doesn't
demonstrate all functionality, but the core is there:

http://www.screencast.com/users/karel1980/folders/Jing/media/0fbfeec9-2db5-49a0-bbaa-6ee381c8cf4d

(Note the need to press three different 'save' buttons in the end,
it's a bit annoying, but I don't have a good suggestion how to fix it,
there really are three steps involved - yada yada just thinking out
loud here.)

HTH,
Karel

On Tue, Nov 17, 2009 at 11:50 PM, <Thomas.Connally@...> wrote:

>
> Could someone explain how the attachment workflow works in Daisy 2.3, or
> else please point me to a URL where this is explained. Searching on the
> Daisy site for the word "attachment" did not produce any useful information.
>
> I seem to recall having read that 2.3 supports an easier attachment workflow
> than in previous versions, i.e., you can open a Word or Excel attachment,
> make changes in Word or Excel, then close the document, and Daisy saves your
> changes in the newest version.
>
> however, I cannot find that information anywhere on the Daisy site.
>
> Thanks
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>

Re: daisy Digest, Vol 62, Issue 4

2009-11-17T14:50:50Z

Could someone explain how the attachment workflow works in Daisy 2.3, or else please point me to a URL where this is explained. Searching on the Daisy site for the word "attachment" did not produce any useful information.

I seem to recall having read that 2.3 supports an easier attachment workflow than in previous versions, i.e., you can open a Word or Excel attachment, make changes in Word or Excel, then close the document, and Daisy saves your changes in the newest version.

however, I cannot find that information anywhere on the Daisy site.

Thanks
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Point in time

2009-11-12T09:32:10Z

Hello,

I'm evaluating Daisy CMS for a project to manage a documentation on
legal content.
One of my requirements is be to be able to do a point in time search
(search content by date).

Currently Daisy only index the live version of a document and it is
impossible to do this point in time search.
I'm wondering how hard it would be to add this to daisy?

My plan would be to:
- add a start and end publication date to every version of each document
- the end publication date would be the start publication date of the
next version (to avoid gap in time)
- add to the lucene index these start and end publication date
- index not only the live version but every published version
- modify the search to be able to search by date using the lucene index

At this point the only issue I see is the growth of the lucene index
(but it is a simple matter of correct sizing)

Anyone worked on this feature before? Anyone else interested, would it
be a valuable addition to Daisy?

Thanks

Aurélien Pelletier
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Which version of mysql do you use?

2009-11-12T01:14:39Z

Hi. In Daisy 2.3 certain things (related to namespace management) don't
work well with MySQL 4.x.

We haven't had any complaints about it, but then again not everybody
uses the namespace management
features.

The installer still supports MySQL 4.x but in the future we might
consider removing it.
Is there anyone out there who is still using MySQL 4.x? Would you
consider upgrading to MySQL 5.x?
Would you be worried if future versions of Daisy would not work on 4.x at all?

Looking forward to your input,
Karel
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[JIRA] Updated: (DSY-744) Saving BookDefinition documents always creates new versions

2009-11-10T07:07:21Z

[ http://issues.cocoondev.org//browse/DSY-744?page=all ]

Paul Focke updated DSY-744:
---------------------------

Summary: Saving BookDefinition documents always creates new versions (was: Saving BookDefinition documents always create new versions)

> Saving BookDefinition documents always creates new versions
> -----------------------------------------------------------
>
> Key: DSY-744
> URL: http://issues.cocoondev.org//browse/DSY-744
> Project: Daisy
> Type: Bug
> Components: Daisy Books
> Versions: 2.4
> Reporter: Paul Focke
> Priority: Minor

>
> When saving documents of the type bookdefintion a new version is created disregarding if changes have actually been made or not.
> It seems like the save function of the PartEditorHelper doesn't always check if there are differences between the old & new versions of the part.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[JIRA] Created: (DSY-744) Saving BookDefinition documents always create new versions

2009-11-10T07:07:21Z

Saving BookDefinition documents always create new versions
----------------------------------------------------------

Key: DSY-744
URL: http://issues.cocoondev.org//browse/DSY-744
Project: Daisy
Type: Bug
Components: Daisy Books
Versions: 2.4
Reporter: Paul Focke
Priority: Minor

When saving documents of the type bookdefintion a new version is created disregarding if changes have actually been made or not.
It seems like the save function of the PartEditorHelper doesn't always check if there are differences between the old & new versions of the part.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: Array of Links as a Daisy Document Field?

2009-11-09T06:29:18Z

On Mon, Nov 9, 2009 at 3:14 PM, John Stubing <jstubing@...> wrote:
> Hello, does anybody know how to create an array of links as a daisy document
> field?

Create a new field, choose type='link', then check the 'multivalue' checkbox?

I know if you set the field type to string you can later set that
> field to a string array, but it doesn't seem to work the same way for links
> (VariantKeys). Has anybody ever done such a thing?

It should work exactly the same. Note that you can only specify the
multivalue property
when creating a field (that's the same for strings and for links), you
can't change it once it's created.

If you really need to change it, create a new field, use a document
task to set the initial values (wrap the
current single-values in an array and set the new field) - search the
archives for code samples.

HTH,
Karel

>
> Thank you.
>
> - John
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>

Array of Links as a Daisy Document Field?

2009-11-09T06:14:00Z

Hello, does anybody know how to create an array of links as a daisy document field? I know if you set the field type to string you can later set that field to a string array, but it doesn't seem to work the same way for links (VariantKeys). Has anybody ever done such a thing?

Thank you.

- John

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[JIRA] Created: (DSY-743) Editor for publication properties is broken

2009-10-26T05:41:21Z

Editor for publication properties is broken
-------------------------------------------

Key: DSY-743
URL: http://issues.cocoondev.org//browse/DSY-743
Project: Daisy
Type: Bug
Components: Daisy Books
Versions: 2.3
Reporter: Karel Vervaeke
Priority: Minor

See PublicationTypesFormHelper.java;
some of code refers to widgets named 'name' and 'value' and others refer to widgets named 'nameUnion', 'editor, 'type-editor', 'required',
resulting in NPE's here and there.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: Question regarding the 255 character limit for a String Field type

2009-10-18T23:56:55Z

In general, when fields tend to get that long, you really should
consider using a part instead of a field. (Alternatively you can
consider a multivalue string field, but usually that's not a very nice
solution.)

If you want to go ahead changing the length limit, there are a number
of locations where Daisy would need to be chaged.

At the very minimum (just to patch your local installation),
- change the limit in the repository database, table thefields, column
stringvalue.
- in the daisy installation directory, change the limit imposed in
fieldtype_to_widgetdefinition.xsl.

HTH,
Karel

On Fri, Oct 16, 2009 at 8:42 PM, Alex Bleasdale <rhodlite78@...> wrote:

>
> Hi,
>
> I'm hoping someone can help,
>
> I've created several Field types as strings and wanted to know whether there
> is there any way to raise their 255 character limit?
>
> Thanks in advance,
> A
> --
> View this message in context: http://www.nabble.com/Question-regarding-the-255-character-limit-for-a-String-Field-type-tp25929926p25929926.html
> Sent from the Daisy - General mailing list archive at Nabble.com.
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>

Question regarding the 255 character limit for a String Field type

2009-10-16T11:12:08Z

Hi,

I'm hoping someone can help,

I've created several Field types as strings and wanted to know whether there is there any way to raise their 255 character limit?

Thanks in advance,
A

Matthew Barbarello is out of the office.

2009-10-16T04:46:32Z

I will be out of the office starting 10/16/2009 and will not return until
10/19/2009.

I will respond to your message when I return.

If this has to do with a Technical Publications issue, please contact
Thomas Connally.

For questions or comments on the Functional Requirements template, please
contact Dhruv Gupta and James Chan.

Thank you.

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[JIRA] Created: (DSY-742) Support for discrete facets on DATETIME expressions

2009-10-15T05:44:21Z

Support for discrete facets on DATETIME expressions
---------------------------------------------------

Key: DSY-742
URL: http://issues.cocoondev.org//browse/DSY-742
Project: Daisy
Type: New Feature
Components: Frontend - faceted browser
Versions: 2.3
Reporter: Karel Vervaeke
Priority: Minor
Fix For: 2.4

Currently, discrete datetime facets are not supported. Defining a discrete date facet on a datetime field (or daisy builtin property such as creationTime) doesn't do the trick:

When you define use type='DATE' on a datetime expression (in the facetednavdef), the facet is rendered fine, showing the timestamp ranges, but when you click on a range, you get this error:
Received exception from repository server.
Error performing query.
Invalid datetime value: "2009-10-15".
Unparseable date: "2009-10-15"

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[JIRA] Created: (DSY-741) Editor change: Linkfields are automatically contextualized to the branch and language of the containing document

2009-10-14T03:14:21Z

Editor change: Linkfields are automatically contextualized to the branch and language of the containing document
----------------------------------------------------------------------------------------------------------------

Key: DSY-741
URL: http://issues.cocoondev.org//browse/DSY-741
Project: Daisy
Type: Task
Reporter: Marc Portier
Priority: Minor

The editor in 2.3 introduced a new link-editor that changed behavior concerning the branch and language of the edited link-fields.

Since 2.3 apparently the editor will automatically replace any set branch and language values in link-fields to -1 if the values match those of the containing document.

For most practical cases this should not be a problem since clients are expected to always contextualize the -1 values with respect to the branch/language values of the containing document.
* See http://daisycms.org/javadoc/daisy/2.3/org/outerj/daisy/repository/Field.html#getValue()
* Also note the handy 2.3 addition: http://daisycms.org/javadoc/daisy/2.3/org/outerj/daisy/repository/Document.html#contextualiseVariantKey(org.outerj.daisy.repository.VariantKey)

(in fact we should consider adding a /**@see javadoc between those)

The effect for future branching/translating of the containing document seems useful, but occasionally not desired. Making it configurable (on the level of the site? the linkfield?) might make sense?

Additionally we probably should check the consistency of this behavior
* on linkfields that are hierarchical and/or multivalue
* on links that are embedded in the daisy-html

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

Re: daisy 2.0.1 hangs without error

2009-10-14T01:44:17Z

On Wed, Oct 14, 2009 at 9:35 AM, Bart Van den Abeele
<bvda@...> wrote:
> Hi,
>
> I don't have a good feeling that upgrading just will fix the issue. I doubt
> it seriously. You give no clear reason why that would fix this issue.
Two years of development time is no clear reason, but it is a very
good reason to at least try an upgrade and to see if it fixes your
problem.

> 2 years back we also needed a stable product. I would rather feel out why my
> repo hangs and act on that but without a clear indication of the error that
> is very hard. You talk about jmx-monitoring and other stuff. How do i set
> this up?
Google is your friend. Search for "jmx monitoring" and "garbage
collection logging" respectively to find out which properties.
Once jmx monitoring is enabled you need jconsole or another similar tool.

> My guess is that it has to do with the cache : 10k docs (these are
> the default right?) and only 256mb ram 100kb/document requires 1024mb ram.
> Wouldn't i get an error of this?
Not having enough ram and a cache size that is much smaller than the
actively consulted set of documents is indeed a possible cause for
problems. I'm not sure which errors you should get.
The wrapper scripts usually log to
${wikidata}/logs/daisy-wiki-service.log and
${repodata}/logs/daisy-repository-server-service.log.

You can also try obtaining a stackdump (using jstack or hitting
ctrl-break with the repository running in a console) when the
repository hangs.

> Any other thoughts?
not immediately. Just gather as much information to analyse as you
can. Be prepared to analyse most of it yourself, I have only limited
time
to assist you on the mailing list.

> Where can i locate the logging of the wrapper-scripts?
The location is described here:
http://www.daisycms.org/daisydocs-2_3/admin/service/330-cd.html

> My college's are working hard with my product and the hangs are far to
> frequent to work fluently. It is starting to annoy them (and me). The
> java-version is 1.6.0.14. I hope we can resolve this issue soon.
As do I

regards,
Karel
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy