Suggestions for hashtag improvements!

Hi @Sushi_Support-Team

Ok, here’s a list of desired features and fixes, in order of importance…

  1. Get syncing to work! We want to be sure that our documents, notes, bookmarks AND folders & categories (!!!) are syncing properly so that our work is being saved, and carrying over from our platforms (iOS & MacOS) and app (for Mac, iPhone, iPad, etc.). As part of that, I’d recommend creating some kind of progress bar / recorded info that shows the last time a file was edited/saved, and with info about the number of notes/annotations, so that we can use this as a reference to determine where the most current annotations of a given file reside, and to ensure that it has been successfully synced. Fixing the sync problems is easily the most urgent problem we face;

  2. Fix and clarify MN folders & categories. Right now it’s glitchy and frankly confusing. No one is clear on how MN’s folder systems is supposed to work, and so there’s a chaotic and problematic file organizational structure in MN (or lack thereof). As a result, many of us have learned to only open files in MN the moment we’re ready to annotate them – otherwise they’ll get lost in a disordered list of files that we’re unable to group and As part of this, we’d like to simple folder / organizational taxonomy in which we’re able to group files by subject AND prioritize them.

  3. Fix all of MN exports – many of us have detailed the various problems with each export format – especially for PDFs (!!!), but also for DEVONthink / RTFs, OmniOutliner, etc.

  4. Get PDF export size down to a manageable size. It’s just way too large to properly use and save as an archived file – or send and share to use as a work product for coworkers & colleagues.

  5. Overall Hashtag set up, referring to the taxonomy - organization approach that I outlined. I think I’ve detailed it enough over here! BTW, I’ve been using TaskPaper as a quick and easy way to create my hashtag taxonomy. Maybe there’s a way for MN to interface with TaskPaper…or you could just refer to it as a simple guide, at the very least…

  6. Create an UID in MarginNote-annotated files – AND, by extension, the notes they create. This will vastly improve the inter-app workflow with such apps as Tinderbox and DEVONthink Pro. For instances such UID’s would help users locate MN-annotated documents and notes in other app’s, and determine where they’d need to be corrected. That would enable users to use the UID to locate the original MN-annotated documents and notes and make corrections, accordingly. Makes sense?

  7. Enable MarginNote’s links to work for internal text for document files (i.e., URL schemes that connect to internal MN-created notes). In other words, enable users to use the MN3-created URL links in other apps (e.g., DEVONthink) – beyond expensive 3rd party apps! (e.g., Mac’s native PDF app, Preview) – so that when we click on MN3-created URL links they’re not opening MarginNote again and, by extension, opening that file online via the iCloud.

  8. Enable MarginNote’s links to be more universally accessible to MN and non-MN users, so that MN users and our colleagues can open them outside of MN, in other apps – apart from expensive 3rd party apps (like PDF Expert) – offline / disconnected from the iCloud;

  9. Refer to my “Search / Find requests (suggestions)” – namely, when using MN’s Search / Find function, the color of the found text is the same as the yellow highlight, so it’s very hard to spot in the document. I’d suggest that MN change the color of the found text, and maybe highlight it with an animated flash (which other apps do nicely). Also, it would be great if there could be a “Find next…” feature, so that one can toggle from one found search word to the next, etc.

  10. Create some kind of Find / Replace function. Also, provide an option to change Smart/Straight quotes. These things are just to help us clean up the text – esp. when the OCR is poor (in MN or another app).

  11. Enable user to just export notes with select hashtags. This would be hugely helpful.

  12. Fix the naming glitch when importing docs into MN so that it doesn’t tack on a number into parentheses.

  13. Redo your user manual! I appreciate some of the online tutorials, but there’s no substitute for a proper written manual.

  14. Create OPML, CSV or Tab-delim exports. For me, it’s a lesser priority now that I’ve changed my work process, but I’ve heard other developers want these export options.

I’m sure there other other suggested repairs and features, but I think this is a good list to start with.

Looking forward to my commission! :wink:

10 Likes