Jump to content

Harald_S

Level 2
  • Content Count

    12
  • Joined

  • Last visited

Everything posted by Harald_S

  1. Thanks for the advice, although I'm not just a newcomer on my job :-). I value Evernote for what it does (spanning platforms mainly) and I 'm introducing it anyway for its pros. There's no blame in posting "sharable obvious primary structuring" as a feature request in a thread called "Post your #1 Feature Request Here!!!". I'm checking the chances of improvement in that respect. I understand that - even though it wouldn't be an irritating feature to offer - it wasn't provided for in the primary concept and it shows up as quite difficult to implement in the meantime with so many databases running otherwise. It might be a compatibility problem and a question of effort and logistics afforded.
  2. Quite OK, one could tag each "subdirectory" accordingly so notes of that level will show up when clicking on the tag. Drawback again: In a client visualizing the shared tag tree the hierarchy of the original is lost and not displayed. Also the introduction of tags by the co-users is not supported.
  3. It is, I made my mind up about that. I'm just trying to push the limits for greater acceptance by my colleagues where practicability within known concepts is an issue.
  4. Thanks for the proposal. You're right, flattening out the directory path into the title is a feasible workaround and probably my means of choice. Nevertheless it's a bit of a drag with growing complexity and only of moderate elegancy ;-). Just imagine a little adjustment in "directory structure" leading to editing all of the titles. Harald
  5. Zumindest gibt's die Export-Funktion der gesammelten Werke in ein einziges Html, suchen kann man dann ja per Suchfunktion, wenn man ein Schlüsselwort weiß. So hab ich's gemacht.
  6. Thanks for appreciating. All the same I am not arguing for academic but for practical reasons. I am trying to establish EN in my company as a communications platform because of its versatileness. The existing options of EN are a very fine assortment of possibilities and of course organisation by tagging is one of them. But for the sake of comprehensive exchange among each other we need a number of specialised notebooks shared in mutual access mode by the competent set of colleagues respectively. Some of them may comprise only two members up to some of them being intended for the whole staff. This is done with premium accounts. But sharing rids from structuring a communications cell (as i may call a specific shared notebook) even by tags, because tagging is restricted to the one and only owner of the notebook, albeit shared as contributable for all members. Also handing around structured datasets (sharing project-containers filled with various files where the layout could be primary information) is restricted when there are just secondary organisational means.
  7. Meaning you agree? Or meaning you're making fun of my arguments?
  8. Allow structuring and sharing of structures. I know I'm not the first one to say so but I'm putting the finger on the point again because of its impact on data organisation which is definitely an aim of Evernote IMHO: The drawback on tag structuring in flat collections is that you only see the immanent structure by searching and not by showing. If you want to share structured information, like projects/circumstances where the structure of presentation is part of the information itself a) it forces you to put all information/notes into a single notebook, because there are no overall tags once shared the structure within has to be outlined by a "keynote" or people won't know the structure inferred otherwise by obvious organisation This means that Evernote generally is more applicable for sharing collections than constructions. Nevertheless the concept of "inheriting" context by nesting entities of understanding is quite a natural real world model, not so much just "old" thinking habit. Why is the flat structure hung up so highly as basic concept for Evernote?
  9. The drawback on tag structuring in flat collections is that you only see the immanent structure by searching and not by showing. If you want to share structured information, like projects/circumstances where the structure of presentation is part of the information itself a) it forces you to put all information/notes into a single notebook, because there are no overall tags once shared the structure within has to be outlined by a "keynote" or people won't know the structure inferred otherwise by obvious organisation This means that Evernote generally is more applicable for sharing collections than constructions. P.S. The concept of "inheriting" context by nesting entities of understanding is quite a real world model and natural, not so much just "old" thinking habit.
  10. Hi, ich habe mir z.B. eine Textseite zusammenkopiert mit KeePass-"Geheimnissen", die ich gerne überall unkompliziert parat hätte. Ist halt in einer einzigen Note. Da sagt man einfach Ctrl-A (alles markieren) und Ctrl-Shift-X (Markierung verschlüsseln) und das Ding ist codiert. Wenn du alle Keepass-Einheiten jeweils in extra Notes haben willst, geht das so nicht, da ausschließlich Passagen codiert werden. Zum Verändern muss man es halt freistellen und nachher wieder verschlüsseln, was wenig Aufwand ist. Hab ich dir aber wohl nix Neues gesagt, außer dass es nicht geht, was du willst ;-). Harald
  11. I guess a good feature might be a synching option per note. Synching manually on the client leads to a general procedure taking a lot of time and overhead, just for staying close to time in a - let's say "conversation". "chatting" on shared notes is really a ponderable feature.
  12. Hi, I have Evernote starting with Windows, but without being logged in automatically for reasons of security and choice. Everytime I reboot Evernote-Video is talking out of the box and it can't be shut off by options. A friend of mine crashes with the video start (!!) so he can't even log in with the client. It would be a nice feature to start the video on demand only. Harald
×
×
  • Create New...