For site notes to be true comments to the site, it should be possible to easily specify what node (and alias) they refer to. At least that's what I imagined after reading the module description (but before installing it).

So, when a sitenote is created, a relevant node field should be offered (if it is created from a link in the sitenotes block, the field should be automatically pre-populated, as well as the alias, if any.

A taxonomy addition would be nice too, since some notes would refer to things like "theme" or "CSS", or "maintenance" or gods know what. Should I split this into a separate feature request?

Comments

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Hmm... While I can see that someone might want to use site notes this way, I have never seen it done. They have always been separate information about the site or how to use it. I have not seen anyone want to use it as a comment to a node.

I'm going to suggest you check out a couple of other modules and see if they might help you. This is a simple module and I'd like to keep it that way if possible.

I can't see any reason why it wouldn't handle taxonomy now - as is. In actuality, had it not been for the original menu problem, this module would have just been a "technique" page in the handbook using a vocabulary, access control, and a View. Site notes are really nothing more than "stories" with a special menu entry and a bit of access control.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Active » Postponed

Oops: Node Comment

andrabr’s picture

andrabr commented

Node Relativity seems to have promise. Thanks for the pinter!

Although (just for the sake of argument), how is Site Notes different from having, say, an admin-only book?

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Site Notes was developed for "simpler" sites that don't otherwise need an access control solution (and there are many Drupal sites like this). It's primary reason for existence was that the menu item wouldn't stay hidden in a core Drupal installation. If you have a way to keep the content away from prying eyes then you can develop another solution that meets your needs using that mechanism. I haven't done much with D6 yet, but there is some promise that either D6 or D7 will eliminate the need for this module.

geste’s picture

geste commented

Nancy,

I can think of a node-specific scenario that led me to this discussion: We now have a page that lists monthly timesheets (and makes them available for download) and it should work in perpetuity .... so long as people name the uploaded PDFs in exact agreement with a convention: timesheet-yyyymm.pdf (like timesheet-200812.pdf for this month).

I would liek to add a little README to the node that would spell out what the rules are for people who can edit the node and upload/attach new files, but I figure it would be polite to hide that from regular vistors.

So I can see a decent use of notes on a node-specific basis. Make sense?

J

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Hmm, maybe. Have you tried adding help text for those nodes - it would show when they edit or create it.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Also keep an eye on http://drupal.org/node/207647

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Postponed » Closed (won't fix)

I may revisit this in the future, but for now, I'm not inclined to work on it.