Talk:ESciDoc Search Index Names

Faces

• In my opinion, this is not relevant for Faces, because in Faces we only have very clear indexes (one per attribute).--Kristina 10:17, 6 February 2009 (UTC)

Ok, but even in this case we have clear naming convention for face indexes such as:

     *faces.emotion instead of escidoc.emotion
     *faces.age instead of escidoc.age

• I think we need an index to search within an album. And more generally we need an index to search within a container. We have indeed only one way to do it currently: write IDs of all members in the query. For Faces it becomes very problematic with very big albums. For example, http://qa-faces.mpdl.mpg.de/album/escidoc:113634, which has 2056 members (the whole collection), takes about 4 minutes to be searched. Since in case of Faces we use the search to browse an album, the user needs about 4 minutes for each page of the album. It is really not acceptable.--Bastien 16:56, 18 March 2009 (UTC)

ViRR

Section moved to VIRR Development Page

General

• Perhaps it makes sense to add escidoc to beginning of indexes, like:

*escidoc.publication.compound.creator
*escidoc.faces.album.creator

because then we could also query like

*escidoc.compound.creator

Possible use case: find all escidoc items where Mr. X was creator of.

*escidoc.compound.title delivers all title on first level 
 **(publication.title, publication.alternativetitle, virrelement title, etc. )

*escidoc.any.title 
 **deliviers all title elements in all escidoc items

• i would not use the term "qualified path" to refer to something like "publication.title". to me qualified path sounds like qualified name in xml terminology, which actually does mean a localname plus a namespace. so "unqualified path" would be more intuitive for me.--Robert 16:58, 11 March 2009 (UTC)

ThnX. Will fix it.

Coordinated Universal Time

Virtueller Raum Reichsrecht