Tweets are the smallest entity of operations and, of course, represent a single (scheduled) Twitter-Tweet. Tweets must always be contained in groups and can thereby be organized by topic. Management of Tweets is loosely implemented as CRUD-interface; You can add (CReate), edit (Update) and delete (Delete) Tweets. A Tweet can take different states: Scheduled and waiting for publication, successfully published and a genuine error-state (e.g. if You schedule a Tweet into the past).
The general overview shows all Tweets in tabular form and makes it easy to identify the group-mapping, Tweet content, image attachment, geolocation, status, Tweet date and possible actions (from left to right). The detailed view of one single Tweet on the other hand shows all data of a single Tweet fully expanded. The difference between the two views is mainly the presentation of information regarding each Tweet. From within both views, all actions regarding a single Tweet (detailed view, edit and delete) may be initiated.
When adding a new Tweet, the following information has to be provided: The group-mapping, Tweet content and scheduled date. Beyond that, an image attachment (as URL) and a geolocation may be specified. As all Tweets must be contained in groups, the input-field for group-mapping is required to be filled. You can either enter the name of a group, that will be created ad-hoc for the Tweet, or reference an existing group by ID (from the dropdown-list).
All added Tweets can be edited, as long as they have not been published. Further, the group-mapping and scheduled date cannot be modified as they are fixed upon Tweet-creation. Other than that, the form to edit a Tweet is the same as the one to add a new Tweet.
Uniting Tweets by topic, groups work quite like directory tree folders. Their management is loosely implemented as a CRUD-interface, like the Tweet-management. Groups can be created while creating a Tweet, as ad-hoc group, they can be created as empty containers for Tweets and they are created when importing Tweets from a source. Further, groups can be enabled and disabled. If a group is disabled, Tweets within this group are not published, even if their scheduling would require them to. Therefore, You have to remember to enable the groups You create or import, if You wish for their Tweets to be published.
Viewing groups, as viewing Tweets, can be done in an tabular overview and detailed mode. Both modes provide access to all applicable actions for the respective group and propagate the same information.
It's fairly simple to add a new group, just input the desired title and description for the group and hit the save button.
Just like when creating a new group, when editing a group You can manipulate the group title and description.
When a group contains Tweets, which are applicable not only to their currently scheduling, but may as well be published again e.g. next year, You can duplicate that group. There are two modes of duplication, You can shorthand-copy a group to the following year or You can specify a new reference date. The first option selects the earliest Tweet from the group and copies it to the specified date and copies all later Tweets to their respective scheduling, keeping the period between the earliest Tweet and the following Tweets constant. The second option performs the following: When You copy a group to a new reference date, You select one Tweet from the group, which is copied to the specified date. All surrounding (earlier and later) Tweets are copied to their respective scheduling, again, keeping the peeriod between the selected Tweet and any surrounding Tweets constant.
One mayor feature of this application is the ability to import large sets of Tweets automatically, either from a Wikipedia-article or TSV-file. In both cases, a new group is created, containing all parsed Tweets. This group has to be activated by the user manually after the impurt succeeded. Please be aware that importing Tweets from Wikipedia may bear differing results, as parsing natural language is still far from perfected.
Using the GoogleDrive public API, You can import a specifically layouted spreadsheet by just supplying the URL of Your publicly shared spreadsheet. You can use this template to quickly create a spreadsheet with Your own Tweets. When You have filled in Your data, just share the sheet via link, as described here, and paste that link to the autoChirp import-form for GoogleDrive sources.
One way of adding a set of Tweets without going through the manual workflow for each Tweet, is to import Tweets from (the German or English) Wikipedia. This is achieved by submitting the Wikipedia-import form containing the URL to the Wikipedia-article to be parsed along with the desired group title and description and possibly a prefix. The referenced article will then be computed, all extracted dates will be used to schedule a Tweet with the sentences containing the extracted date as Tweet-content.
Probably the most effective way to add huge sets of Tweets, possibly with image attachment and geolocation, is importing them from a TSV (tab-separated-values) file. The format of the file has to be exactly as follows (a comma represents a tab in the actual file): Date, time, Tweet content, image attachment, latitude, longitude. Uploading files which do not concur to this format will result in errors.
As advertised on the landing page of this application, autoChirp has the handy ability to render text into an image and attach this image to a Tweet. For ease of usability, this feature is automatically applied to all of Your Tweets exeeding Twitters 140 character limit. As autoChirp also offers to attach custom images to Your Tweets but can only append one image due to API limitations, Your image will be included in the flashcard.