Repository capabilities - Merge FullText values into Query

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: Schema
    • None
    • Hide

      We should get rid of FullText, by just making the values of "Query" as follows:

      Query (non-Boolean) Indicates the types of queries that the Repository has the ability to fulfill. Query support levels are:

      • None: No queries of any kind can be fulfilled.
      • MetadataOnly: Only queries that filter based on object properties can be fulfilled.
      • FulltextOnly: Only queries that filter based on the full-text content of documents can be fulfilled.
      • BothSeparately: The Repository can fulfill queries that filter based on object metadata and/or document full-text content, but not in the same query.
      • Both: The Repository can fulfill queries that filter based on object metadata and document full-text content in the same query.
      Show
      We should get rid of FullText, by just making the values of "Query" as follows: Query (non-Boolean) Indicates the types of queries that the Repository has the ability to fulfill. Query support levels are: None: No queries of any kind can be fulfilled. MetadataOnly: Only queries that filter based on object properties can be fulfilled. FulltextOnly: Only queries that filter based on the full-text content of documents can be fulfilled. BothSeparately: The Repository can fulfill queries that filter based on object metadata and/or document full-text content, but not in the same query. Both: The Repository can fulfill queries that filter based on object metadata and document full-text content in the same query.
    • Hide

      Duplicate - already done

      Show
      Duplicate - already done

      In the CMIS domain model/schema, we currently have two "capabilities" relating to full-text support in search. These are:

      Query (non-Boolean) Indicates the types of queries that the Repository has the ability to fulfill. Query support levels are:

      • None
      • MetadataOnly: Only queries that filter based on object properties can be fulfilled.
      • FulltextOnly: Only queries that filter based on the full-text content of documents can be fulfilled.
      • Both: The Repository can fulfill queries that filter based on object metadata and/or document full-text content.

      FullText (non-Boolean)
      Indicates the types of full-text queries that the Repository has the ability to fulfill. FullText support levels are:

      • None: No full-text queries can be issued.
      • FullTextOnly: Only queries that filter based on the full-text content of documents can be fulfilled.
      • FullTextAndStructured: The repository can fulfill queries that filter on both the full-text content of documents and their properties.

      This is unnecessarily complicated. There are redundant states and inter-dependency between the values (e.g. there are two full-text only values, and FullTextAndStructured only makes sense for Fulltext if "both" is the value for Query).

            Assignee:
            Unassigned
            Reporter:
            Ethan Gur-esh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: