Difference between revisions of "TruxtonCommunication"

From truxwiki.com
Jump to navigation Jump to search
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
This class lets you add to the communication items (email/sms/mms) to Truxton.
 
This class lets you add to the communication items (email/sms/mms) to Truxton.
This will populate the <code>Message</code>, <code>MessageAddress</code>, and other tables in the database.
+
This will populate the <code>[Message]</code>, <code>[MessageAddress]</code>, and other tables in the database.
 
=Attributes and Methods=
 
=Attributes and Methods=
==<code>addparticipant(account, role)</code>==
+
==<code>addnote(text: str) -> boolean</code>==
 +
This adds an investigator's note.
 +
The <code>text</code> parameter is the contents of the note.
 +
It will return
 +
[https://docs.python.org/3.10/library/constants.html?highlight=false#True True] if the tag was associated with the communication, [https://docs.python.org/3.10/library/constants.html?highlight=false#False False] on failure.
 +
The note is stored in the <code>[InvestigatorNote]</code> table in the database.
 +
 
 +
==<code>addpiece(file: object, origin: int, instance: int) -> boolean</code>==
 +
This allows you to add a [[TruxtonFileIO|file]] or [[TruxtonChildFileIO|child file]] as part of a communication.
 +
The <code>origin</code> parameter should be one of the [[Origin|defined constants.]]
 +
 
 +
==<code>addparticipant(account: str, name: str, role: int, artifact_type: int) -> str</code>==
 
After <code>save()</code> has been called, you add the participants to the message.
 
After <code>save()</code> has been called, you add the participants to the message.
 
The <code>account</code> is the phone number or email address or account that participated in the message.
 
The <code>account</code> is the phone number or email address or account that participated in the message.
 +
The <code>name</code> is the name of the person associated with this account or an empty string.
 
The <code>role</code> parameter is the <code>[[Message Participants|MESSAGE_PARTICIPANT]]</code> constants.
 
The <code>role</code> parameter is the <code>[[Message Participants|MESSAGE_PARTICIPANT]]</code> constants.
 +
The <code>artifact_type</code> is used when the underlying function automatically adds the account to the artifacts table.
 +
It should be one of the [[Entity Types|defined constants]].
 +
It should be a value that matches the <code>[ID]</code> column of the <code>[MessageAddressType]</code> table.
  
==<code>fileid</code>==
+
==<code>fileid: str</code>==
 
The [https://en.wikipedia.org/wiki/Universally_unique_identifier GUID] of the file this event came from.
 
The [https://en.wikipedia.org/wiki/Universally_unique_identifier GUID] of the file this event came from.
This corresponds to the <code>FileID</code> column of the <code>Message</code> table.
+
This corresponds to the <code>[FileID]</code> column of the <code>[Message]</code> table.
  
==<code>finished()</code>==
+
==<code>finished() -> boolean</code>==
This should be called after you have finished adding pieces to this message.
+
This should be called after you have finished adding all of the pieces to this message.
 +
It will return [https://docs.python.org/3.10/library/constants.html#True True] if the record was saved to the database, [https://docs.python.org/3.10/library/constants.html#False False] if there was an error.
  
==<code>id</code>==
+
==<code>id: str</code>==
 
This is the [https://en.wikipedia.org/wiki/Universally_unique_identifier GUID] of the event.
 
This is the [https://en.wikipedia.org/wiki/Universally_unique_identifier GUID] of the event.
 
It becomes non-zero after <code>save()</code> has been called.
 
It becomes non-zero after <code>save()</code> has been called.
  
==<code>mediaid</code>==
+
==<code>mediaid: str</code>==
 
This is the [https://en.wikipedia.org/wiki/Universally_unique_identifier GUID] of the media this event came from.
 
This is the [https://en.wikipedia.org/wiki/Universally_unique_identifier GUID] of the media this event came from.
This identifier corresponds to the <code>MediaID</code> of the <code>Message</code> table.
+
This identifier corresponds to the <code>[MediaID]</code> of the <code>[Message]</code> table.
  
==<code>received</code>==
+
==<code>received: [https://docs.python.org/3/library/datetime.html datetime]</code>==
When the message was received in [https://docs.microsoft.com/en-us/windows/win32/api/minwinbase/ns-minwinbase-filetime FILETIME] ticks.
+
When the message was received.
This corresponds to the <code>Received</code> column of the <code>Message</code> table.
+
This value can be set with either a datetime value or an integer representing [https://docs.microsoft.com/en-us/windows/win32/api/minwinbase/ns-minwinbase-filetime FILETIME] ticks.
 +
This corresponds to the <code>[Received]</code> column of the <code>[Message]</code> table.
  
==<code>save()</code>==
+
==<code>save() -> boolean</code>==
This will commit the information to the <code>Event</code> table.
+
This will commit the information to the <code>[Message]</code> table.
 +
It will return [https://docs.python.org/3.10/library/constants.html#True True] if the record was saved to the database, [https://docs.python.org/3/library/constants.html#False False] if there was an error.
  
==<code>sent</code>==
+
==<code>sent: [https://docs.python.org/3/library/datetime.html datetime]</code>==
When the message was sent in [https://docs.microsoft.com/en-us/windows/win32/api/minwinbase/ns-minwinbase-filetime FILETIME] ticks.
+
When the message was sent.
This corresponds to the <code>Sent</code> column of the <code>Message</code> table.
+
This value can be set with either a datetime value or an integer representing [https://docs.microsoft.com/en-us/windows/win32/api/minwinbase/ns-minwinbase-filetime FILETIME] ticks.
 +
This corresponds to the <code>[Sent]</code> column of the <code>[Message]</code> table.
  
==<code>subject</code>==
+
==<code>subject: str</code>==
 
The subject of the message.
 
The subject of the message.
 
If the message type is SMS or MMS, this is the text of the message.
 
If the message type is SMS or MMS, this is the text of the message.
This corresponds to the <code>Text</code> column of the <code>MessageSubject</code> table.
+
This corresponds to the <code>[Text]</code> column of the <code>[MessageSubject]</code> table.
  
==<code>tag(tag, reason, origin)</code>==
+
==<code>tag(tag: str, reason: str, origin: int) -> boolean</code>==
 
This creates a tag associated with this event in Truxton.
 
This creates a tag associated with this event in Truxton.
 
The <code>tag</code> parameter is a short, one or two word, bit of text that will be displayed in the UI.
 
The <code>tag</code> parameter is a short, one or two word, bit of text that will be displayed in the UI.
The <code>reason</code> a sentence explaining why this event was tagged.
+
The <code>reason</code> is a sentence explaining why this event was tagged.
 
The <code>origin</code> is either <code>TAG_ORIGIN_AUTOMATIC</code> (1) or <code>TAG_ORIGIN_HUMAN</code> (2).
 
The <code>origin</code> is either <code>TAG_ORIGIN_AUTOMATIC</code> (1) or <code>TAG_ORIGIN_HUMAN</code> (2).
 
It will return  
 
It will return  
[https://docs.python.org/3.8/library/constants.html?highlight=false#True True] if the tag was associated with the file, [https://docs.python.org/3.8/library/constants.html?highlight=false#False False] on failure.
+
[https://docs.python.org/3.10/library/constants.html?highlight=false#True True] if the tag was associated with the file, [https://docs.python.org/3.10/library/constants.html?highlight=false#False False] on failure.
  
==<code>type</code>==
+
==<code>type: int</code>==
 
The type of message.
 
The type of message.
It is one of the <code>[[Message Types | MESSAGE_TYPE]]</code> constants.
+
It is one of the <code>[[Message Types|MESSAGE_TYPE]]</code> constants.
This corresponds to the <code>MessageTypeID</code> column of the <code>Message</code> table and should be a value from the <code>ID</code> column of the <code>MessageType</code> table.
+
This corresponds to the <code>[MessageTypeID]</code> column of the <code>[Message]</code> table and should be a value from the <code>[ID]</code> column of the <code>[MessageType]</code> table.
  
 
=Sample=
 
=Sample=
 +
<source lang="Python" highlight="3-7,9-10,19,31,36">
 +
def add_message(parent_truxton_file):
 +
communication = parent_file.newcommunication()
 +
communication.sent = ticks("2015-08-16T21:31:37-00:00");
 +
communication.received = communication.sent
 +
communication.subject = "Dinner at 8?"
 +
communication.type = truxton.MESSAGE_TYPE_SMS
 +
communication.save()
  
<syntaxhighlight lang="Python" line highlight="3-7,9-10,12">
+
communication.addparticipant("703.555.1212", truxton.MESSAGE_PARTICIPANT_FROM, truxton.ENTITY_TYPE_PHONE_NUMBER)
def add_message(parent_truxton_file):
+
communication.addparticipant("202.555.1212", truxton.MESSAGE_PARTICIPANT_TO, truxton.ENTITY_TYPE_PHONE_NUMBER)
  communication = parent_file.newcommunication()
+
 
  communication.sent = ticks("2015-08-16T21:31:37-00:00");
+
body1 = root_file.newchild()
  communication.received = communication.sent
+
body1.name = "Body.txt"
  communication.subject = "Dinner at 8?"
+
body1.origin = truxton.ORIGIN_EMAIL_BODY
  communication.type = truxton.MESSAGE_TYPE_SMS
+
body1.type = truxton.Type_ASCII_Text
  communication.save()
+
body1.write('Hello World')
 +
body1.save()
 +
 
 +
if not communication.addpiece(body1, truxton.ORIGIN_EMAIL_BODY, 1):
 +
    print("Body not saved")
 +
else:
 +
    print("Body was saved")
 +
 
 +
attachment1 = root_file.newchild()
 +
attachment1.name = "Attachment.txt"
 +
attachment1.origin = truxton.ORIGIN_EMAIL_ATTACHMENT
 +
attachment1.type = truxton.Type_ASCII_Text
 +
attachment1.write('Goodbye World')
 +
attachment1.save()
 +
 
 +
if not communication.addpiece(attachment1, truxton.ORIGIN_EMAIL_ATTACHMENT, 1):
 +
    print("Attachment not saved")
 +
else:
 +
    print("Attachment saved")
  
  communication.addparticipant("703.555.1212", truxton.MESSAGE_PARTICIPANT_FROM)
+
communication.finished()
  communication.addparticipant("202.555.1212", truxton.MESSAGE_PARTICIPANT_TO)
 
  
  communication.finished()
+
return None
</syntaxhighlight>
+
</source>

Latest revision as of 11:07, 16 April 2025

This class lets you add to the communication items (email/sms/mms) to Truxton. This will populate the [Message], [MessageAddress], and other tables in the database.

Attributes and Methods

addnote(text: str) -> boolean

This adds an investigator's note. The text parameter is the contents of the note. It will return True if the tag was associated with the communication, False on failure. The note is stored in the [InvestigatorNote] table in the database.

addpiece(file: object, origin: int, instance: int) -> boolean

This allows you to add a file or child file as part of a communication. The origin parameter should be one of the defined constants.

addparticipant(account: str, name: str, role: int, artifact_type: int) -> str

After save() has been called, you add the participants to the message. The account is the phone number or email address or account that participated in the message. The name is the name of the person associated with this account or an empty string. The role parameter is the MESSAGE_PARTICIPANT constants. The artifact_type is used when the underlying function automatically adds the account to the artifacts table. It should be one of the defined constants. It should be a value that matches the [ID] column of the [MessageAddressType] table.

fileid: str

The GUID of the file this event came from. This corresponds to the [FileID] column of the [Message] table.

finished() -> boolean

This should be called after you have finished adding all of the pieces to this message. It will return True if the record was saved to the database, False if there was an error.

id: str

This is the GUID of the event. It becomes non-zero after save() has been called.

mediaid: str

This is the GUID of the media this event came from. This identifier corresponds to the [MediaID] of the [Message] table.

received: datetime

When the message was received. This value can be set with either a datetime value or an integer representing FILETIME ticks. This corresponds to the [Received] column of the [Message] table.

save() -> boolean

This will commit the information to the [Message] table. It will return True if the record was saved to the database, False if there was an error.

sent: datetime

When the message was sent. This value can be set with either a datetime value or an integer representing FILETIME ticks. This corresponds to the [Sent] column of the [Message] table.

subject: str

The subject of the message. If the message type is SMS or MMS, this is the text of the message. This corresponds to the [Text] column of the [MessageSubject] table.

tag(tag: str, reason: str, origin: int) -> boolean

This creates a tag associated with this event in Truxton. The tag parameter is a short, one or two word, bit of text that will be displayed in the UI. The reason is a sentence explaining why this event was tagged. The origin is either TAG_ORIGIN_AUTOMATIC (1) or TAG_ORIGIN_HUMAN (2). It will return True if the tag was associated with the file, False on failure.

type: int

The type of message. It is one of the MESSAGE_TYPE constants. This corresponds to the [MessageTypeID] column of the [Message] table and should be a value from the [ID] column of the [MessageType] table.

Sample

def add_message(parent_truxton_file):
 communication = parent_file.newcommunication()
 communication.sent = ticks("2015-08-16T21:31:37-00:00");
 communication.received = communication.sent
 communication.subject = "Dinner at 8?"
 communication.type = truxton.MESSAGE_TYPE_SMS
 communication.save()

 communication.addparticipant("703.555.1212", truxton.MESSAGE_PARTICIPANT_FROM, truxton.ENTITY_TYPE_PHONE_NUMBER)
 communication.addparticipant("202.555.1212", truxton.MESSAGE_PARTICIPANT_TO, truxton.ENTITY_TYPE_PHONE_NUMBER)

 body1 = root_file.newchild()
 body1.name = "Body.txt"
 body1.origin = truxton.ORIGIN_EMAIL_BODY
 body1.type = truxton.Type_ASCII_Text
 body1.write('Hello World')
 body1.save()

 if not communication.addpiece(body1, truxton.ORIGIN_EMAIL_BODY, 1):
    print("Body not saved")
 else:
    print("Body was saved")

 attachment1 = root_file.newchild()
 attachment1.name = "Attachment.txt"
 attachment1.origin = truxton.ORIGIN_EMAIL_ATTACHMENT
 attachment1.type = truxton.Type_ASCII_Text
 attachment1.write('Goodbye World')
 attachment1.save()

 if not communication.addpiece(attachment1, truxton.ORIGIN_EMAIL_ATTACHMENT, 1):
    print("Attachment not saved")
 else:
    print("Attachment saved")

 communication.finished()

 return None