Things I might find interesting in an email client or environment. Raw thoughts.
- fast search
- search inside encrypted emails
- get related and linked stuff easily at any time during reading
- easily organise windows and content, e.g.
- when you select to reply to an email, put the draft next to the original so that you don’t need to switch windows
- use a consistent style when commenting inline
- easily create tasks and notes from parts of emails
- organise / order following user’s workflow
- by people, topic, tone of content, project, task, event
- integrate with business process(es)
- suggest while typing
- spelling and grammar
- references to other emails / notes / events / conversations
- people to include as recipient
- named entities
- expansions of abbreviations
- different tone of text by using templates
- replacement text
- find and use embedded machine-actionable information
- explain what the client did to your experience
- log observations and following actions by the mail user agent
- show the reasons for suggesting stuff
If you, like me, a) have a large collection of music files on your computer and b) you manage (and play) them through iTunes and c) have a MusicBrainz account to do some metadata normalisation, have you thought of this?
Suppose you want to export your ratings to the MusicBrainz server so that eventually you can import them to another music player, let MusicBrainz Picard embed your ratings in the files or just share them (not having them public but still on the server is not possible). Perhaps this could work:
- Use MusicBrainz Picard to tag MP3 files with MusicBrainz recording (previously track) identifiers
- Export the iTunes library – it will now be a plist XML file
- Optional(?): Convert the exported iTunes library to normal XML
- Extract a list of file names and MusicBrainz identifiers from the files
- Extract a list of file names and ratings from the (converted, if necessary) iTunes library
- Send for each of the MusicBrainz identifiers with a rating the rating to the MusicBrainz server
Why haven’t I done this yet? Well, priorities lie elsewhere. I’m not convinced I want all my ratings online, although I may want to use my rating information in other applications in the future. Perhaps they’re of use during the Public Broadcasting hackathon November 9 – what if an application could match me to a radio station playing the music I like?
Step 1 will take a lot of time, because my collection is far from fully covered by MusicBrainz. Step 2 is easy. Step 3 has at least a potential solution. Step 4 can be handled by a shell script that I don’t have yet. Step 5 can be performed by an XQuery or XSLT transformation. Step 6 needs a script that calls the MB REST service with input.
Or are there better ways?
I’ve had some ideas for things and things to do at some point in the future, but I can’t do all of them at the same time and most ideas need more thought (and research). I’ll list them here, not ordered by priority in any case, hopefully to inspire more ideas and spark discussion.
Continue reading “To do (excerpt): redesign, catalogue, PIM-KB, Semantic EPUB”
Yes, I’m on LinkedIn, and yes, in the past I have supplied even my Gmail password to LinkedIn to let it pull in all my contacts. I don’t believe I made LinkedIn send everyone an email. Back in the days, I had the option to see who else was on LinkedIn (by email address) and invite people to connect manually. I felt bad afterwards that I had entered my password and still see traces of my address book in LinkedIn.
Maybe I should delete my LinkedIn profile and put more effort in sharing details more selectively. Details about myself (I don’t have a Facebook account and try to be selective with what I share on Twitter), but details about my network too, need not necessarily be public. I don’t need others like LinkedIn to make money off the information I’m providing explicitly and implicitly. I’m not sure though, how to balance keeping private information private and have some kind of public profile for others to refer to. Or maybe that should be: for other to exploit like LinkedIn exploits my information currently.
Maybe I should try the old way: link people on my website, endorse them by writing something nice about them and their work, but only if we all agree that’s a Good Thing™. Would you want that?
Let me describe ArticLib. It is a vision to share printed articles without much overhead and save paper and printer toner in the long term. Continue reading “ArticLib: share and save paper in the office/library/…”