If you have requested an export of your Tameday data - it will be supplied as a ZIP file - containing a series of XML files.
Once the ZIP file is extracted - it will have a structure like below:
Each section is briefly explained below – including a section of the XML code produced.
This contains all the users within a Tameday account.
UserID Unique identifier per user and used to link the user to projects, to-dos, events etc
AvatarURL URL of the image for the users avatar
StatusID 0 = Invited 1 Live 4 Archived
UserType 0 = Staff 1 = External
IsAdmin 0 = Normal user 1 = Admin user
This contains each Team – and the users within them. Example below shows Users 1 and 2 are part of the Company HQ team.
TeamID Unique identifier per team
StatusID 1 Live 4 Archived
ProjectID Team project identifier – see Projects
This contains all companies within a Tameday account.
CompanyID Unique identifier
This is a list of all contacts (Staff & External) - and includes contact address next of kin, social media info etc – if set. Social Media types are also exported at the end of this XML.
ContactID Unique identifier
CompanyID ID that links to company’s info (see companies section above)
ContactType 0 = Staff 1 = External
ContactUserID ID that links to Users info (see user section above)
SocialTypeID ID that links to a specific type e.g. 1 Twitter 2 Facebook etc
This is a list of all projects within a Tameday account. This includes company projects, Team projects and Locker (personal projects). It also contains the list of users assigned to each project.
ProjectID Unique identifier
StatusID 1 = Live 2 Complete 4 Archived
IsTeam 0 = no 1 = yes, it is a team project (see teams section above)
UserID Links to the user info (see users section above)
This is a list of the inbox items from within Tameday.
InboxID Unique identifier
UserID Links to user info to define which user it belongs to (see users section above)
HasAttachment 0 no 1 yes. If yes – additional xml will show URL, file size etc
IsRead 0 no 1 yes it has been viewed already
ProjectID Link to projects if inbox item is within a project inbox (see projects above)
IsComplete 0 no 1 yes
Each file contains a list of to dos (and to do posts) per project.
e.g. Project_41_ToDos.xml contains all the to dos within project 41.
List information is also shown at the bottom of the XML.
ToDoID Unique identifier
ProjectID Links to projects
CreatedBy User that created the to do – links to user info
StatusID 0 draft 1 live 2 complete 4 archived
ListID Link to lists info to determine which list a to do belongs to.
PostID Unique identifier for each post within a to do
UserID User that posted the comment – see user info section
Assigned 0 not assigned 1 assigned
This is a list of discussions, files & notes within your Tameday account – per project.
e.g. Project_33_Discussions.xml contains discussions/files etc within Project 33.
It also contains all the document types at the bottom of the XML.
DiscussionID Unique identifier
ProjectID Link to projects
CreatedBy UserID of the person who created the discussion/posted the file
Links to Users info
IsNote 0 no 1 yes, it is a note
IsDocument 0 no 1 yes, it is a document/file
IsFolder 0 no 1 yes it is a folder
PostID Unique identifier for each post on that discussion/note etc
UserID User that posted the comment
DocumentTypeID Determines the type of file posted e.g. 2 PDF 3 Google Doc etc
This is a list of all events within your Tameday account – per project.
e.g. Project_93_Events.xml contains all the event information for project ID 93.
It also contains a list of event types at the end of the XML.
EventID Unique identifier
EventType ID to denote the type of the event e.g. 1 meeting 2 appointment etc
CreatedBy UserID of the user who created the event
StatusID 1 live 4 archived
ProjectID Links to projects info
EventPrivate 0 no 1 yes, it is a private event
PostID Unique identifier for each post/comment
UserID User who posted the comment – links to Users info