Timestamped Field Notes has too many configuration options. I know that, and I should likely trim some, but there are a varied use cases for the application, and I’d like to support those which I can. Further, I know that most users don’t adjust (or even know about) the default configuration settings, and that likely reduces the value of features placed behind a configuration option. All true, but where we are today…
Search enabled – allow text search into events and/or notes.
Notes Grouping – group notes by the hour, day, or more…
Event Grouping – group events by the hour, day, week, month…
I use the application to monitor raptors, observing Peregrine Falcons, Prairie Falcons and Golden Eagle in the Rocky Mountains. I go hike, observe and record, export the data to submit with my report and move on. I do group notes and events, just for easier visually scanning. I don’t need search, I don’t go back and look at past entries. I do not have search enabled.
Others do. Some people use the application to record events, as a log. For them search allows them to quickly answer questions of “when did X occur”, either which events contained this note, or even which notes contained that text.
Go to “Manage” / “Configure Application” to get to the application settings.
Text to insert into the event to mark each interval
… and a few others.
These can be associated with an event or a keyword set (to have it apply to each event created with those keywords.)
Intervals are presented on the screen (see screenshot) as a count down above the data entry fields. Intervals can be paused, restarted and/or reset – where the start of interval time is changed to now.
This feature is entering beta testing phase, and anybody willing to give their feedback on this feature – to see if it works well for their uses – is asked to express their interest to email@example.com.
I’ve received some interest in “interval timers” for Timestamped Field Notes, i.e. regular audible blips, notifications and/or automatic text inserts that occur at time intervals during the event data entry. The purpose is to segment the data, or initiate regular action from the user.
This feature would help support behavioral sampling (e.g. scan sampling, instantaneous sampling) but maybe also other purposes for your need.
If interested in helping specify this feature, please comment here, or send your thoughts to firstname.lastname@example.org or answer these quick questions: