Thanx reifsnyderb,

I'll keep an eye on this thread and make my comments and help with testing as I deal alot with document/file management and developed a records management system/workflow for physical records using formulize mod which is also great mod.

reifsnyderb

Have you enabled swish-e in the config file ?
Entered the path ?
Created an index ?

It is functional if these are done correctly. For me, I had to
manually enable the full-text search feature in mysql (write
config has issues for me), figure out path to swish-e (my
swish-e path is /usr/bin), enter the path into config,
(maybe directly into mysql, don't remember), then goto the repository
directory (that's where _binfilter.sh should be) and execute the swish-e index. (a function on swish-e side, found
instructions online).

Took a little doing, not plug and play, but after the index is
created it works like a charm. Well worth the effort.

I'm going to learn more about swish-e, it has a lot of
functionality, I'd love to incorporate into website search
function.

Hello,

I just posted version 1.95 at http://www.blitzenware.com/download/dms-1.95.tar.bz2

Regards,

Brian

Quote:
Did anybody try Sphinx? I would be curious how does it compare to Swish-e. It seems to be more actively developed than Swish-e.

I went to the the Sphinx website. They have no searching ?
That's funny.

Didn't see an index files spider like feature in the docs for
Spinx, so I went to google/advanced, and searched the terms

spider AND index

I found this on a forum...

"I was wondering if I can use this to spider multiple websites. As nice as it is to create a search engine for my own information, I am creating a website and would like to search a couple of websites that aren't mine (it's not against their TOS) for data purposes.

I am sure that answer is around here somewhere but I thought I would ask just to be certain."

Answer:
"Sphinx does not include any Web spider. But you could of course use some 3rd party spider to fetch the documents and put them into database, and then index that database."

It looks blazing fast with huge amounts of data, but appears
dependent on a database and won't spider.

___________

From what I've read about swish-e you can search meta-data, xml, have multiple indexes, can limit to document sets, and spiders off-site.

Also found a benchmark on mysql vs. swish-e full text
searching, at http://joshr.com/src/docs/IndexingWithSwishe-Rabinowitz.pdf. Looking for a Swish-e, Spinx comparison.

Is a full text query searching something to be concerned
about ? I tend to look for the least query intensive alternative.
Not sure if it's a valid concern. Any thoughts ?

And a question, anyone familiar wit Tesseract OCR, google
open source ocr.

Thanks for the DMS upgrade. I have been using ver 1.91.

I have installed the upgrade, working under xoops 2.5.4 with
full text search.

Installed with debub on, fixed a few can't write to files or folder errors. Also, you have a file, don't remember which, if Linux lines
commented out, had to uncomment to make it work.

Admin doesn't work from the admin panel, you get a blank screen. You have to go into admin from the module page, options/admin.

But, can't do much there. I had to make most configs directly
in mysql. But the module works great.

Also, the package doesn't have the swish-e docs, had to
copy over from the earlier version.

Making full-text search work:

1. Edit swish-e.conf doc, change index dir and index file to
point to to your repository directory.

2. Change FileFilter .dat to
FileFilter .dat "your-path-to-repository/_binfilter.sh" "'%p'"

3. compile the search index.
From console run: swish-e -c swish-e.conf -f index.swish-e

4. enable full text searching in config.

5. Point to swish-e path in config. e.g., for me it's /usr/bin for me

Couldn't make cofig changes in module page/admin . The
write configuration files fails to write with few exceptions.

I am getting an error, possibly related config not writing.
"Notice: Undefined variable: dms_config in file /modules/dms/inc_dms_functions.php line 907"

I say this is possibly related because I cannot enable comments, and and config_main.php refers to "dms_config" relative to enabling
comments. The can't find dms_config error may explain, just
a guess, why I have little luck in writing to the config file.

config_main.php says
$query = "UPDATE ".$dmsdb->prefix('dms_config')." SET
data = '".dms_get_var_chk("chk_comments_enable")."' WHERE name='comments_enable'"; $dmsdb->query($query);

I went to the mysql cofig table, there is no chk_
comments_enable field ? Can I enable it directly in mysql ?

Hello,

You can add the chk_comments_enable row directly in mysql. That isn't a problem.

This module has never been tested past Xoops 2.0.x, so I really don't know how well it will work with newer versions.

I'll have to get a dev environment setup so that I can take a look at it. It will probably be some weeks, however.

Regards,

Brian

I'm not finding a chk_comments_enable field in the
database. I see nothing to enable comments.

As for working, I've used version 1.91 with similar methods
of install on production and development sites without issue.
As a module, it seems stable with room for improvement.
The next version of Xoops may be a different story.

But yes, I realize it's untested. I'm running on a development
site, largely dependent on a DMS. I'm hoping your next
version will be ready before I am.

That aside, it's a great module. I'm just sharing the experience.

Thank you.

I do have one question... when you click on and goto a
folder, folder_expand strips folder_id= from the address.
As a result the back button does not work. Would you
share the line of code that makes that happen ?

B.T.W. the new search full text results is much nicer :)

Nice to see the reactions after an everyone thought "lost" developer states he wants to renew the good old module DMS. I can't wait

Hello,

The chk_comments_enable item needs to be added in the xoops_dms_config table as:

name = chk_comments_enable
data = 0

i.e.
insert into xoops_dms_config values ('chk_comments_enable','0');

The xoops_dms_config table was designed in this fashion to allow more options to be easily added. Looking through the update manager, it appears that I missed adding this update.

Also, the data from this table is cached. So, You can either close out of and re-open your browser or set the xoops_dms_config timestamp item to '0' so that it re-loads the cached configuration. (The configuration caching was done in order to cut down on mysql query data passed between the web server and the database server.)

Using the browser navigation buttons was not encouraged in the environment in which this module was deployed. So, unfortunately, there isn't any support for using the back button.

Regards,

Brian




Quote: