Skip to content
  • There are no suggestions because the search field is empty.

Metadata Classification Appendix

An appendix to the metadata classification guide containing repository specific anomalies

This appendix lists the anomalies that may occur for each repository type supported by ActiveNav Cloud when using Metadata Classificationopen_in_new.

File Size Oddities

Google Drive

Google Drive previously reported all proprietary file formats as zero-byte files when returning information from the API. However, our most recent Google discovery testing shows file sizes in both personal and shared drives. It is unclear whether this reflects a Google-wide policy change, but it is included here for awareness.

When the collector discovers Google Forms constituent parts, none of the API responses provide a size therefore they will all report as 0.

Teams

When retrieving Teams Channel messages, the length of the message in character count is used as the size.

ShareFile

ShareFile has a proprietary entity called a Note, this always reports as a 0 byte file.

Current Date Fallbacks

Windows File Share

Only repository where all dates are retrieved from target data, should never be null.

SharePoint and OneDrive

  • Created - Can be null.
  • Modified - Can be null, will fall back to Created if null.
  • Accessed - Does not exist, will fall back to Modified (and Created if null).

Teams

  • Team/Channel - Only created exists, can be null. Created is used for Modified/Accessed.
  • Posts virtual folder - All dates are null.
  • Message/Folder/File - Same as SharePoint/OneDrive.

Exchange

  • User - Only created exists, can be null. Created is used for Modified/Accessed.
  • Mail Folder - All null.
  • Mail Message -
    • Created - Sent Date - can be null.
    • Modified - Received At - can be null (falls back to created when null).
    • Accessed - Does not exist, falls back to Modified (and Created if null).

Google

  • Created - can be null.
  • Modified - can be null, will fall back to Created if null.
  • Accessed - does not exist, will fall back to Modified (and Created if null).
  • Forms -
    • Virtual container, Form Details and Form Image take their dates from the 'file' object found in the drive, so rules above apply (they would all be null otherwise).
    • Form Response -
      • Created is available but can be null.
      • Modified is last submitted time, can be null and falls back to created.
      • Accessed does not exist and will fall back to modified (and created if null).

ShareFile

  • Personal Folder -
    • Created - Created.
    • Modified has two options of client edit date and progeny edit date, it takes the most recent of the two.
    • Accessed - falls back to Modified.
    • All can be null, no other fallbacks.
  • Folder/Object/Note -
    • Created takes client created date, if null falls back to progeny created date.
    • Modified and Accessed follow same rule as Personal Folder.

iManage

  • Library/Client - All dates null
  • Workspace -
    • Created and Modified exist (API documentation says they will not be null).
    • Accessed uses Modified.
  • Folder -
    • Created date does not exist, set to null.
    • Modified exists (API documentation says will not be null).
    • Accessed uses Modified.
  • File -
    • Created will use fileCreatedDate if exists, otherwise use createDate.
    • Modified will use most recent of fileModifedDate and modifiedDate (API documentation states that these will not be null).
    • Accessed uses Modified.

If file is an email then sent date is used as created if it exists, otherwise fall back to File logic. Received date is used as modified if it exists, otherwise falls back to file logic.

NetDocuments

  • Repository/Cabinet/Parent Attribute (Client)/Various virtual folders - All null, no dates available.
  • Workspace/Top Level Folder/Folder/File -
    • Created and Modified both exist but can be null, no fallback logic.
    • Accessed uses Modified.