From: Samuel Wales <email@example.com> To: "Ross A. Laird" <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Re: Item ranking system? Date: Fri, 3 Jul 2009 14:57:11 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> One thing to think about is global vs. local. Global priorities (or properties -- I am not talking about implementation here) are sorted in the agenda. Thus an A in an unimportant part of the hierarchy is the same as an A in an important part. Local priorites are just for siblings. They are for sorting in the outline. You don't want to confuse that with global priorities. It is very useful. Inheritance is different and IMO a can of worms. For me, it's not worth the complexity so far. It would be a feature of global priorities if it were implemented. It makes no sense for local priorities unless you decide on exheritance. (Min, mean, max, median, sum, and other schemes are possible, but probably not worth the complexity.) But I wanted to point out that sorting siblings requires a different priority space than sorting in the agenda. IMO it would be great as something like - #[A] for global A (this is the current syntax) - #[,A] for local A (ignored by the agenda) - #[A,A] for both global A and local A so that you can directly see the local priority on the headlines just as you do now with global priorities, but to implement local priorities without changing org, you can use properties or tags. Just stuff to think about or ignore. On Fri, Jul 3, 2009 at 12:55, Ross A. Laird<firstname.lastname@example.org> wrote: > Matthew Lundin <email@example.com> writes: > >> Ian Barton <firstname.lastname@example.org> writes: >> >>> Ross A. Laird wrote: >>>> I'm sure there are many ways in org to accomplish my goal with this >>>> particular project, which is to create a ranking system for items. >>>> Here's the situation: I have about 200 items that I am evaluating. I >>>> need each item to have a title, a tag, a note, and a ranking from 0 to >>>> 5. Then, I need to be able to sort the items by rank, with items ranked >>>> 5 at the top. I know that I can do this using tables in org, but I >>>> prefer the flexibility of headings (some of the items might have long >>>> notes attached to them, or links, or whatever). Also, I don't think I >>>> can tag individual cells in a table, or operate on cells the way I can >>>> with headings in org (move, refile, show and hide, etc.). So, I'm >>>> looking for something that will allow me to have the best of worlds: >>>> flexibility as with headings, and numerical sorting as with table cells. >>> >>> What about making them all TODO items and using the priority filed for >>> sorting. I don't use priorities myself, so I am not sure if you can >>> change A, B, C, etc to 1, 2, 3. >> >> The easiest way to set custom priorities is to do so in the buffer. You >> could simply add the following line to the top of the relevant file: >> >> #+PRIORITIES: 1 5 3 >> >> This line sets 1 as the highest priority, 5 as the lowest priority, and >> 3 as the default priority. >> >> Then, once you have added priorities such as the following... >> >> * A list >> ** [#5] Some item >> ** [#4] Another item >> ** [#2] Yet another item >> >> ...you can sort them by calling org-sort (C-c ^ p) on the heading. (C-c ^ >> P will sort them in reverse order.) >> >> The other option here would be to create a "ranking" property for each >> item with predefined entry options. You would still be able to sort the >> list, but you could also view it as columns and capture it in a table >> using dynamic blocks. (Of course, you could also display the priorities >> above in column view.) >> >> #+PROPERTY: RANKING_ALL 1 2 3 4 5 >> #+COLUMNS: %40ITEM %10RANKING >> >> * Some item >> :PROPERTIES: >> :RANKING: 3 >> :END: >> * Another item >> :PROPERTIES: >> :RANKING: 1 >> :END: >> * Yet another item >> :PROPERTIES: >> :RANKING: 5 >> :END: >> >> Best, >> Matt >> > > Thanks for all the helpful responses. This list is great. > > Cheers. > > Ross > > -- > Ross A. Laird, PhD > Chair, Department of Creative Writing > Faculty, Interdisciplinary Expressive Arts > Kwantlen Polytechnic University > > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacsemail@example.com > http://lists.gnu.org/mailman/listinfo/emacs-orgmode > -- Myalgic encephalomyelitis is causing death and severe suffering. Conflicts of interest are destroying research. You can get the disease at any time and die from it. Do science and justice matter to you? http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
next prev parent reply other threads:[~2009-07-03 21:57 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-03 18:04 Ross A. Laird 2009-07-03 18:16 ` Ian Barton 2009-07-03 18:36 ` Matthew Lundin 2009-07-03 19:55 ` Ross A. Laird 2009-07-03 21:57 ` Samuel Wales [this message] 2009-07-03 18:21 ` Nick Dokos 2009-07-03 18:46 ` Nick Dokos
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Re: Item ranking system?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).