Digital tickler 📅 ✨ 🗂
- Monitors a directory containing YYYY-MM-DD-files-or-folders
- Moves the files or folders to your inbox (e.g., the Desktop) when you start the computer.
- Can also use template directories to create and activate material on a regular basis.
Think about
- Activate my flight-tickets for printing two days before the flight.
- Activate a PDF for the meeting on Tuesday.
- Activate project x in two weeks.
- Activate template y every Friday for a planning-and-review session (or Getting-Things-Done).
- Want to make decisions on new commitments not on an ad-hoc basis but when you think about the broader picture, i.e., in a weekly or monthly session? Just move them to the next weekly or monthly folder that is automatically created and activated.
Features
- Cross-platform, tested on Ubuntu.
- Based on flat files, no additional database. Easy to backup and restore.
- Supports symlinks to avoid moving large files or folders (and triggering long sync-processes of Dropbox).
- Automatically creates and updates bookmarks in Nautilus (Linux) if regular template-directories are provided.
Installation
pip install digital-tickler
Setup
- Add 'digital_tickler' or start_tickler.sh to system-autostart.
- When the script is called for the first time:
- Provide a tickler-path. This is a directory in which files or folders starting with YYYY-MM-DD- are stored. These files will be automatically moved to the inbox-path when the script is executed on YYYY-MM-DD (or any time after this date).
- Provide an inbox-path. This is the directory to which the files and folders are transferred on YYYY-MM-DD. Choose a directory that you check regularly, such as the Desktop.
- Optional: provide paths for template_weekly_path, template_monthly_path, template_semester_path, template_annual_path. The script will copy the template directories to the tickler-path on a regular basis, e.g., for regular review-and-planning sessions.
Similar Projects
https://github.com/golliher/dg-tickler-file/blob/master/daily_tickler.py
License
MIT License.
History
0.0.2 (2021-09-35)
- Use versioneer.
0.0.1 (2021-09-23)
- First release on PyPI.
Metadata
Release files for digital-tickler 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| digital_tickler-0.0.3.tar.gz | 27.3 kB | Without provenance | Details for digital_tickler-0.0.3.tar.gz |
Release files / digital_tickler-0.0.3.tar.gz
| Download URL | digital_tickler-0.0.3.tar.gz |
|---|---|
| Size | 27.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58def09623df7c678670b594e61f9aba941bc52817a8f9bc515667b4536a8b41
|
|
BLAKE2b-256 checksum How to use checksums |
5c216cea25f1cc41171349de8051bd93ed90b86f639e666d51933eae8354e8a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.14.0 pkginfo/1.7.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.8.10
|
Security for digital-tickler 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.