You are viewing limited content. For full access, please sign in.

Question

Question

Does Laserfiche support Taxonomy integration

Laserfiche Search and Retrieval
Updated January 24, 2017
asked on March 31, 2015

Can Laserfiche support Taxonomy integration. What format(s) can Laserfiche take, if do?

We are thinking about autoclassification and conceptual search that are based on a localized taxonomy. We are hoping laserfiche search can pull out related terms from a taxonomy to suggest relevant search results. We also hope Laserfiche can automatically tag and classify records based on the taxonomy. 

I know SharePoint accept CSV taxonomy to be imported to their SharePoint taxonomy store. I have never heard if Laserfiche can be configured/integrated with a taxonomy.

Thanks for helping!  

 

0 0

Answers

APPROVED ANSWER
replied on April 2, 2015

Hi,

Thank you for your examples. Starting from 9.2.1, thesaurus search is supported. This might meet your requirments.

The thesaurus should be pre-defined. For example, the following thesaurus settings should work for 'recreation center':

<?xml version="1.0" encoding="UTF-8"?>
<ArrayOfThesaurus xmlns="http://laserfiche.com/namespaces/fts/v3">
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">recreation center</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">regional sports development center</string>
    </Terms>
  </Thesaurus>
</ArrayOfThesaurus>

Here is the step-by-step guide to use thesaurus:

1. Prepare an xml file to contain the word list, in following format:

<?xml version="1.0" encoding="UTF-8"?>
<ArrayOfThesaurus xmlns="http://laserfiche.com/namespaces/fts/v3">
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">recreation center</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">regional sports development center</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">LFFTS</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">Full-Text Search Engine</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">Laserfiche Full-Text Indexing and Search Engine</string>
    </Terms>
  </Thesaurus>
</ArrayOfThesaurus>

2. Set thesuarus with lfftscfg.exe: 

"C:\Program Files\Laserfiche\LFFTS\lfftscfg.exe" setthesaurus {catalogUUID} {thesaurusXmlPath}

3. Try: search either "recreation center" or "regional sports development center", they should return same results.

1 0
SELECTED ANSWER
replied on July 22, 2015

Hello Ben,

 

It is currently not supported to import thesaurus sets from other applications, like LibreOffice/OpenOffice/WordNet. We will add it to our feature backlog.

 

At this point, Laserfiche doesn't support pos (part of speech or other meaning specific description; like noun and verb in your example) information for thesaurus. The thesaurus set in your example should be converted to the following XML file:

 

<?xml version="1.0" encoding="UTF-8"?>
<ArrayOfThesaurus xmlns="http://laserfiche.com/namespaces/fts/v3">
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">tam-tam</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussion instrument</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussive instrument</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">chime</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">bell</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">sound</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong buoy</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">bell buoy</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">acoustic buoy</string>
    </Terms>
  </Thesaurus>
</ArrayOfThesaurus>

 

Note that the duplicates (percussion instrument, and percussive instrument appear twice in the original file) in the first Terms element are removed. Otherwise, the XML file would be rejected by the search engine.

 

When using WordNet (LibreOffice/OpenOffice) style thesaurus sets, Laserfiche search engine may also behave differently: it expands equivalence terms automatically. This means chime and sound, in your example, are also considered as thesaurus. This is a side effect of auto expanding. Its purpose is to make it easier to build up thesaurus set manually. Adding more control of auto expanding is also in our backlog. In addition to this, auto expanding means the following XML file also works:

 

<?xml version="1.0" encoding="UTF-8"?>
<ArrayOfThesaurus xmlns="http://laserfiche.com/namespaces/fts/v3">
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">tam-tam</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussion instrument</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussive instrument</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">chime</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">bell</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussion instrument</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussive instrument</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">sound</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong buoy</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">bell buoy</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">acoustic buoy</string>
    </Terms>
  </Thesaurus>
</ArrayOfThesaurus>

 

1 0

Replies

replied on January 24, 2017

Hi,

We have supported more Taxonomy related features in Laserfiche 10.2. For example, import thesaurus from SharePoint managed metadata files and OpenOffice thesaurus files. The configuration page is in the Laserfiche Web Administration Console 10.2.

Please note, the thesaurus schema has been changed in 10.2. Now there's no symmetry between Key and Synonym, and it's non-transitive. After upgrading to Laserfiche 10.2, the thesaurus set before upgrading will not be available, and you need to re-configure it.

1 0
replied on April 1, 2015

Hi,

Can you give me some detail use case and real-world scenario? Do you want to assign Laserfiche tags to documents automatically, based on a pre-defined words list? 

With Laserfiche workflow, you can do search using a pre-defined query, then add Laserfiche tags to the result documents. You can run the workflow in a daily basis. Is this helpful?

0 0
replied on April 1, 2015

Thank Xiang. Can I take the answer as No?

Language is a living thing and constantly evolving.  Building name changes because the funder changes. Although the building is the same building, documents about the same building are titled after different building names.

For a leaking incidence, people can create documents and title them after leaking, flood, leakage, seepage, outpouring. Or pavement construction and over lay construction.

Just to name a few. certainly we can have users manually tag (user generated tags), but there is no consistency.  Tags can go really wild. We also don't want to force controlled vocabulary. RM don't want to have more enemies. We want the system understands relations between terms out of natural human language.

My ultimate goal is:

When I search recreation center, records about the regional sports development center can be returned as well. 

 

I cannot believe that Laserfiche can not be integrated with any types of taxonomy.

Should I lower my expectation?

 

0 0
APPROVED ANSWER
replied on April 2, 2015

Hi,

Thank you for your examples. Starting from 9.2.1, thesaurus search is supported. This might meet your requirments.

The thesaurus should be pre-defined. For example, the following thesaurus settings should work for 'recreation center':

<?xml version="1.0" encoding="UTF-8"?>
<ArrayOfThesaurus xmlns="http://laserfiche.com/namespaces/fts/v3">
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">recreation center</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">regional sports development center</string>
    </Terms>
  </Thesaurus>
</ArrayOfThesaurus>

Here is the step-by-step guide to use thesaurus:

1. Prepare an xml file to contain the word list, in following format:

<?xml version="1.0" encoding="UTF-8"?>
<ArrayOfThesaurus xmlns="http://laserfiche.com/namespaces/fts/v3">
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">recreation center</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">regional sports development center</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">LFFTS</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">Full-Text Search Engine</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">Laserfiche Full-Text Indexing and Search Engine</string>
    </Terms>
  </Thesaurus>
</ArrayOfThesaurus>

2. Set thesuarus with lfftscfg.exe: 

"C:\Program Files\Laserfiche\LFFTS\lfftscfg.exe" setthesaurus {catalogUUID} {thesaurusXmlPath}

3. Try: search either "recreation center" or "regional sports development center", they should return same results.

1 0
replied on April 2, 2015

Hi Cangfei,

Thank you for your answer. I know Laserfiche must have a way to integrate Taxonomy or Thesaurus.

1) Is xml the only format that Laserfiche can take?

2) (Setp 2. set thesaurus with lfftscfg.exe) Is it per user based? Can we make server based integration, so it automatically applies to the entire system?

3) Are there established laserfiche taxonomy partners that we can contact?

FYI

http://www.a-k-a.co/index.php/category/product/

http://www.wandinc.com/taxonomies.aspx

Thank you very much for helping!

0 0
replied on April 2, 2015

Hi,

I'm glad that it is helpful.

1) Yes, Laserfiche only supports this schema currently. A help document will be published to Laserfiche support site.
2) The thesaurus is per catalog (repository) basis, which means that all users on this catalog can use the thesaurus. It is supported to use different thesaurus settings on different catalogs.
3) No, there aren't any established Laserfiche taxonomy partners currently. We will add it to our feature backlog. You need to convert the thesaurus generated by other applications to the required schema for now.

0 0
replied on July 21, 2015

Hi Laserfiche,

Is the thesaurus solution compatible with any existing thesaurus sets, such as Libreoffice/OpenOffice?

gong|3
(noun)|tam-tam|percussion instrument|percussive instrument
(noun)|chime|bell|percussion instrument|percussive instrument
(verb)|sound
gong buoy|1
(noun)|bell buoy|acoustic buoy

 

0 0
SELECTED ANSWER
replied on July 22, 2015

Hello Ben,

 

It is currently not supported to import thesaurus sets from other applications, like LibreOffice/OpenOffice/WordNet. We will add it to our feature backlog.

 

At this point, Laserfiche doesn't support pos (part of speech or other meaning specific description; like noun and verb in your example) information for thesaurus. The thesaurus set in your example should be converted to the following XML file:

 

<?xml version="1.0" encoding="UTF-8"?>
<ArrayOfThesaurus xmlns="http://laserfiche.com/namespaces/fts/v3">
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">tam-tam</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussion instrument</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussive instrument</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">chime</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">bell</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">sound</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong buoy</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">bell buoy</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">acoustic buoy</string>
    </Terms>
  </Thesaurus>
</ArrayOfThesaurus>

 

Note that the duplicates (percussion instrument, and percussive instrument appear twice in the original file) in the first Terms element are removed. Otherwise, the XML file would be rejected by the search engine.

 

When using WordNet (LibreOffice/OpenOffice) style thesaurus sets, Laserfiche search engine may also behave differently: it expands equivalence terms automatically. This means chime and sound, in your example, are also considered as thesaurus. This is a side effect of auto expanding. Its purpose is to make it easier to build up thesaurus set manually. Adding more control of auto expanding is also in our backlog. In addition to this, auto expanding means the following XML file also works:

 

<?xml version="1.0" encoding="UTF-8"?>
<ArrayOfThesaurus xmlns="http://laserfiche.com/namespaces/fts/v3">
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">tam-tam</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussion instrument</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussive instrument</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">chime</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">bell</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussion instrument</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">percussive instrument</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">sound</string>
    </Terms>
  </Thesaurus>
  <Thesaurus>
    <Terms>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">gong buoy</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">bell buoy</string>
      <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/Arrays">acoustic buoy</string>
    </Terms>
  </Thesaurus>
</ArrayOfThesaurus>

 

1 0
replied on July 22, 2015

Thanks a lot for your detailed response. :)

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...