It depends on what you are looking for. It's fairly easyto write a report that gets all files that have the"application/octet-stream" or "application/activemessage"mime types. For us, files that were placed in Livelink incorrectly getone of those two mime types. It would be more difficult to find, forexample, all of the Word documents that don't have"application/msword".
Can you give more details on what issues you are experiencing?
From: eLink Discussion:Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Wednesday, June 10, 2009 1:22 PMTo: eLink RecipientSubject: LiveReport to display the documents with wrong mime typesassigned
LiveReport to display the documents with wrong mime types assigned
Posted by kamin@enmax.com (Amin, Khurram ) on 2009/06/10 13:18
I am looking for a LiveReprt that should display the list of all documents having wrong mime type assigned to them? Can someone help me to find that LiveReport? Thanks, Khurram
[To reply to this thread, use your normal E-mail reply function.]
Discussion:
Livelink LiveReports Discussion
Livelink Server:
knowledge-wlweb01
To Unsubscribe from this Discussion, send an e-mail to unsubscribe.livereportsdiscussion@elinkkc.opentext.com.
This SQL query grabs all files (the most recent version) thathave a specified file type and a specified mime type. You could take outone or the other to get a broader list.
select b.docid as "Node ID", b.mimetype as"Mimetype", a.name as "Name", b.filetype as"Filetype", a.createdate, a.modifydate as "ModDate",c.lastname, c.name
from dtree a, dversdata b, kuaf c
where a.userid = c.id and a.dataid=b.docid anda.versionnum=b.version and b.filetype='doc' and b.mimetype='application/octet-stream'
order by c.lastname
So for example, I ran a query with just the b.filetype='doc',and got less results than I did with b.mimetype='application/msword'. So that shows that there are a bunch of documents, with the Word mime type,that do not have a file extension of Word. Some of them are rtf files,which makes sense. If I was motivated, I would go and fix them all J
Keep in mind I have not tried to run this as a LiveReport. I have only run it in SQL Server Mgmt Studio.
From: eLink Discussion:Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Wednesday, June 10, 2009 3:41 PMTo: eLink RecipientSubject: I was looking if the Livelink system assign any wrong mime typeto the document...
I was looking if the Livelink system assign any wrong mime type to the document...
Posted by kamin@enmax.com (Amin, Khurram ) on 2009/06/10 15:40
In reply to: RE RE LiveReport to display the documents with wrong mime types assigned
Posted by timothy.hunter.ctr@wpafb.af.mil (Hunter, Tim ) on 2009/06/10 13:41
I was looking if the Livelink system assign any wrong mime type to the document either its octet-stream or anyother that is not related to the actual document type.
Topic:
Hello Khurram,
The default configuration of Livelinkprefers the MIME type of the document as provided by the client overDCS-detected MIME type or MIME type based on file extension (by referencing themime.types file). If incorrect MIME types have been associated with documents,it is most likely due to the fact that the browser / application used to pushfiles into Livelink sent the wrong MIME type in the request.
Unless you have a comprehensiveassociation of file extensions <--> MIME types for all possible file extensionsused in your Livelink cluster, preparing a LiveReport for this purpose seemsimpractical. Since filenames can be renamed by users at will, some files maynot even have an associated extension to compare against without looking backat the original filename at the time the document was uploaded to Livelink. Thisoriginal filename is stored in the DVersData table.
One thing to keep in mind as an example…just because a file has a “.doc” extension does not necessarilymean it’s a Word document.
-- Kyle
From: eLinkDiscussion: Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Wednesday, June 10, 20093:41 PMTo: eLink RecipientSubject: I was looking if theLivelink system assign any wrong mime type to the document...
FYI, the “filetype” stored inDVersData is simply the extension on the file at the time it was uploaded.
Again, if a file has an extension of “.doc”(hence a filetype of ‘doc’), that does not mean that the fileshould have the MIME type ‘application/msword’.
From: eLinkDiscussion: Livelink LiveReports Discussion[mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Wednesday, June 10, 20094:08 PMTo: eLink RecipientSubject: RE I was looking if theLivelink system assign any wrong mime type to the document...
RE I was looking if the Livelink system assign any wrong mime type to the document...
Posted by nbride (Bride, Nicole) on 2009/06/10 16:07
In reply to: I was looking if the Livelink system assign any wrong mime type to the document...
Message from Bride, Nicole <nbride@cvps.com> via eLink
This SQL query grabs all files (the most recent version) that have a specified file type and a specified mime type. You could take out one or the other to get a broader list.
select b.docid as "Node ID", b.mimetype as "Mimetype", a.name as "Name", b.filetype as "Filetype", a.createdate, a.modifydate as "ModDate", c.lastname, c.name
where a.userid = c.id and a.dataid=b.docid and a.versionnum=b.version and b.filetype='doc' and b.mimetype='application/octet-stream'
So for example, I ran a query with just the b.filetype='doc', and got less results than I did with b.mimetype='application/msword'. So that shows that there are a bunch of documents, with the Word mime type, that do not have a file extension of Word. Some of them are rtf files, which makes sense. If I was motivated, I would go and fix them all J
From: eLink Discussion: Livelink LiveReports Discussion [mailto:livereportsdiscussion@elinkkc.opentext.com] Sent: Wednesday, June 10, 2009 3:41 PMTo: eLink RecipientSubject: I was looking if the Livelink system assign any wrong mime type to the document...
