ManifoldCF
  1. ManifoldCF
  2. CONNECTORS-44

Adding metadata support to JDBC connector

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JDBC connector
    • Environment:

      Windows, Oracle 10g, Oracle Universal Content Management System

      Description

      The metadata for the documents checked in is stored in different fields of the Database. for example created date, Author,Title etc.

      The BLOB object contains only the text of the document. It would be very helpful if we could add support select Metadata fields (Columns in the database ) while querying the table.

      The above support would be helpful and make it a substitute for Oracle UCM (Stellent) Connector.

        Activity

        Hide
        Antony Lovric added a comment -

        I like that idea, I'm going to work on this more next week, when I get into the guts I'll let you know.

        Show
        Antony Lovric added a comment - I like that idea, I'm going to work on this more next week, when I get into the guts I'll let you know.
        Hide
        Karl Wright added a comment -

        If you can provide schema details, I can either extend the JDBC connector to support security, or (even better) we can create a dedicated UCM connector that knows about the stellent schema and doesn't require a user to know it.

        Show
        Karl Wright added a comment - If you can provide schema details, I can either extend the JDBC connector to support security, or (even better) we can create a dedicated UCM connector that knows about the stellent schema and doesn't require a user to know it.
        Hide
        Antony Lovric added a comment - - edited

        Hi Rohan, I know Manifold works with SOLR, and Stellent integrates with LDAP but the part I can't connect is getting the association of Document<->LDAP Role(s). Maybe I can look at the Stellent schema and figure that out. Thanks for the comment, I think this might have started a thought...

        Show
        Antony Lovric added a comment - - edited Hi Rohan, I know Manifold works with SOLR, and Stellent integrates with LDAP but the part I can't connect is getting the association of Document<->LDAP Role(s). Maybe I can look at the Stellent schema and figure that out. Thanks for the comment, I think this might have started a thought...
        Hide
        Rohan G Patil added a comment -

        Hi Antony,

        Nope I did not manage to integrate the Connector with Stellent's security, Stellent offers out of the box LDAP security, maybe you could try to integrate that with Manifold.

        Show
        Rohan G Patil added a comment - Hi Antony, Nope I did not manage to integrate the Connector with Stellent's security, Stellent offers out of the box LDAP security, maybe you could try to integrate that with Manifold.
        Hide
        Antony Lovric added a comment - - edited

        Rohan, did you manage to integrate the connector with Stellent's security? I am looking into options for integrating Manifold with Stellent (Oracle UCM) but none seem to respect Stellents' security model.

        Show
        Antony Lovric added a comment - - edited Rohan, did you manage to integrate the connector with Stellent's security? I am looking into options for integrating Manifold with Stellent (Oracle UCM) but none seem to respect Stellents' security model.
        Hide
        Rohan G Patil added a comment -

        Regarding this being a Stellent connector.

        I was supposed to write a Oracle UCM (Formally Stellent) repository connector.

        upon searching, i found that oracle fulltext search actually stores all the documents in the database( 2 tables actually IDCCOLL1 and IDCCOLL2), even the data as BLOB and metadata in different columns.

        So i used the JDBC connector as a "substitute" for a stellent connector.

        Show
        Rohan G Patil added a comment - Regarding this being a Stellent connector. I was supposed to write a Oracle UCM (Formally Stellent) repository connector. upon searching, i found that oracle fulltext search actually stores all the documents in the database( 2 tables actually IDCCOLL1 and IDCCOLL2), even the data as BLOB and metadata in different columns. So i used the JDBC connector as a "substitute" for a stellent connector.
        Hide
        Karl Wright added a comment -

        Committed fix in svn revision 953386.

        Show
        Karl Wright added a comment - Committed fix in svn revision 953386.
        Hide
        Karl Wright added a comment -

        The following proposal would meet the requirement, seems to me:

        (1) Rename the internal column names provided by the connector for things like $(IDCOLUMN) to something pretty obscure, e.g. "LCF__ID". This would help prevent unintended collisions.
        (2) For the data query, interpret ALL columns that are not part of the predefined set as being metadata, where the name of the metadata item will be the column's name in the corresponding resultset.

        It seems to me that this would grant sufficient control to the user to do almost anything with the connector, metadata-wise.

        Show
        Karl Wright added a comment - The following proposal would meet the requirement, seems to me: (1) Rename the internal column names provided by the connector for things like $(IDCOLUMN) to something pretty obscure, e.g. "LCF__ID". This would help prevent unintended collisions. (2) For the data query, interpret ALL columns that are not part of the predefined set as being metadata, where the name of the metadata item will be the column's name in the corresponding resultset. It seems to me that this would grant sufficient control to the user to do almost anything with the connector, metadata-wise.
        Hide
        Karl Wright added a comment -

        I think this feature has merit in its own right. I'm a little leery about this becoming a Stellent connector, though, since:
        (a) it's hardly end-user friendly for users to have to learn the Stellent schema;
        (b) I'm sure Stellent has some kind of security, and this proposal would not address that.

        Show
        Karl Wright added a comment - I think this feature has merit in its own right. I'm a little leery about this becoming a Stellent connector, though, since: (a) it's hardly end-user friendly for users to have to learn the Stellent schema; (b) I'm sure Stellent has some kind of security, and this proposal would not address that.

          People

          • Assignee:
            Karl Wright
            Reporter:
            Rohan G Patil
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 48h
              48h
              Remaining:
              Remaining Estimate - 48h
              48h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development