The following shows an example of an AspireObject after fetching the connector source information from the RDB. This is a parent document which is supplied to a scanner.
|AspireObject field name||Type||Description||Publisher Use|
|title||string||The extracted title from the document.||Mapped to the presentation title. Displayed to the user in the search results as the title of the document.|
|content||string||The full content of the document.||Used for full-text search over the entire contents of the document. Typically considered to be the weakest hits (i.e. less strong than any of the grank# fields).|
|fetchUrl||URL||The original URL used to fetch the content from the remote server.||Used as the unique ID of the document if id doesn't exist. If the displayUrl does not exist, then fetchUrl is used as the URL which is displayed in the search results to the user. When clicked by the user, the user will be sent to this Url (again, if displayUrl does not exist).|
|id||String||A unique identifier of the document (usually the URL of the document).||Used as the unique ID of the document.|
|displayUrl||URL||The URL used by a user to access the document.||Used as the URL which is displayed in the search results to the user. If it is not defined, fetchUrl is used for this purpose.|
|url||URL||The URL used during the scan process to uniquely identify a document.||If fetchUrl and id are not present, it's used as the unique ID of the document.|
|lastModified||String Date (ISO8601)||The last modified date of the document.||Used as a sortable field in the search results.|
|dataSize||long||Size of the document.||Used as a description field for the document in the search results.|
|owner||String||Username/name of the owner of the document. The person to refer too when additional information about the document is required.||Used as a description/sortable field for the document in the search results.|
|modifiedBy||String||Username/name of the last user to modify the document.||Used as a description/sortable field for the document in the search results.|
|createdBy||String||Username/name of the user who created the document.||Used as a description/sortable field for the document in the search results.|
|action||String||Action to perform (add/update/delete).||Used to determine what kind of action is going to be performed with the document at the publishers.|
As Processed by Fetching and Metadata Processing
Document produced by the Scanner, which is input to the fetcher.
Plus, any MIME type can be a type.
Can custom applications can have their own types? For example: "customer:wma" for a customer's Work Management Application? - needs further research]
Some expected types for the future: