[jira] Created: (CONNECTORS-44) Adding metadata support to JDBC connector
Adding metadata support to JDBC connector - Key: CONNECTORS-44 URL: https://issues.apache.org/jira/browse/CONNECTORS-44 Project: Lucene Connector Framework Issue Type: Improvement Components: JDBC connector Environment: Windows, Oracle 10g, Oracle Universal Content Management System Reporter: Rohan G Patil Priority: Critical 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONNECTORS-34) eRoom authority and connector
[ https://issues.apache.org/jira/browse/CONNECTORS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877408#action_12877408 ] Karl Wright commented on CONNECTORS-34: --- It turns out that EMC has released a new version of eRoom that uses Documentum as an implementation platform. This would imply that no connector needs to be developed, except perhaps to support legacy eRoom installations. Can anyone confirm this story? > eRoom authority and connector > - > > Key: CONNECTORS-34 > URL: https://issues.apache.org/jira/browse/CONNECTORS-34 > Project: Lucene Connector Framework > Issue Type: New Feature >Reporter: Karl Wright > > eRoom has a SOAP API which looks like it has enough power to perhaps > implement a connector and an authority. The eRoom API url is here (and yes, > it is a chinese url, but is legit): > https://eroom.abraxas.ch/eroomHelp/en/API_Help/Api.htm#home_api.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONNECTORS-44) Adding metadata support to JDBC connector
[ https://issues.apache.org/jira/browse/CONNECTORS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877409#action_12877409 ] Karl Wright commented on CONNECTORS-44: --- 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. > Adding metadata support to JDBC connector > - > > Key: CONNECTORS-44 > URL: https://issues.apache.org/jira/browse/CONNECTORS-44 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: JDBC connector > Environment: Windows, Oracle 10g, Oracle Universal Content Management > System >Reporter: Rohan G Patil >Priority: Critical > Original Estimate: 0.02h > Remaining Estimate: 0.02h > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (CONNECTORS-44) Adding metadata support to JDBC connector
[ https://issues.apache.org/jira/browse/CONNECTORS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-44: -- Original Estimate: 48h (was: 0.02h) Remaining Estimate: 48h (was: 0.02h) Assignee: Karl Wright Priority: Major (was: Critical) > Adding metadata support to JDBC connector > - > > Key: CONNECTORS-44 > URL: https://issues.apache.org/jira/browse/CONNECTORS-44 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: JDBC connector > Environment: Windows, Oracle 10g, Oracle Universal Content Management > System >Reporter: Rohan G Patil >Assignee: Karl Wright > Original Estimate: 48h > Remaining Estimate: 48h > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONNECTORS-44) Adding metadata support to JDBC connector
[ https://issues.apache.org/jira/browse/CONNECTORS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877469#action_12877469 ] Karl Wright commented on CONNECTORS-44: --- 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. > Adding metadata support to JDBC connector > - > > Key: CONNECTORS-44 > URL: https://issues.apache.org/jira/browse/CONNECTORS-44 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: JDBC connector > Environment: Windows, Oracle 10g, Oracle Universal Content Management > System >Reporter: Rohan G Patil >Assignee: Karl Wright > Original Estimate: 48h > Remaining Estimate: 48h > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CONNECTORS-44) Adding metadata support to JDBC connector
[ https://issues.apache.org/jira/browse/CONNECTORS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-44. --- Resolution: Fixed Committed fix in svn revision 953386. > Adding metadata support to JDBC connector > - > > Key: CONNECTORS-44 > URL: https://issues.apache.org/jira/browse/CONNECTORS-44 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: JDBC connector > Environment: Windows, Oracle 10g, Oracle Universal Content Management > System >Reporter: Rohan G Patil >Assignee: Karl Wright > Original Estimate: 48h > Remaining Estimate: 48h > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONNECTORS-44) Adding metadata support to JDBC connector
[ https://issues.apache.org/jira/browse/CONNECTORS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877714#action_12877714 ] Rohan G Patil commented on CONNECTORS-44: - 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. > Adding metadata support to JDBC connector > - > > Key: CONNECTORS-44 > URL: https://issues.apache.org/jira/browse/CONNECTORS-44 > Project: Lucene Connector Framework > Issue Type: Improvement > Components: JDBC connector > Environment: Windows, Oracle 10g, Oracle Universal Content Management > System >Reporter: Rohan G Patil >Assignee: Karl Wright > Original Estimate: 48h > Remaining Estimate: 48h > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
