This is a great module to support arbitrary boolean attributes for nodes. How about extending it to support a string for value.
SO if the bookmark type is string a keyword=value type can be supported which opens up many more possibilities.
e.g
1. Admin can specify node_attribute=nn and only nodes between xx and yy can be shown to different role of readers
2. Depending on the value themes can add different widget. (possible through the taxonomy but this could be more internal)
Basically create a meta data system for nodes (it already is) but support more than just boolean values.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | details_field_2007.tgz | 4.52 KB | dman |
| #6 | details_field_ui.gif | 6.04 KB | dman |
Comments
Comment #1
quicksketchAre you suggesting that bookmarks have more than two states? I'm not sure how the UI would work for something like this, just keep clicking until you get the value you want? If you're just wanting to make the boolean value 'nn' instead of 1, you could just name your bookmarks as 'nn' and then if flagged then it would be an 'nn' value.
I'm still a little fuzzy on what you're trying to request here, but my initial impression is either it's something that can be done already, or it's something that probably shouldn't be implemented.
Comment #2
dman commentedYou're better off with CCK for that.
It's much more robust (sorta) and hooks into real metadata management for sorting & filtering etc like you'd want to do.
Not a bookmarks job IMO.
Comment #3
ajayg commentedI was searching what I wanted to do and came across this interesting article
http://www.whatwoulddrupaldo.org/a-modest-proposal-node-attributes
In the comments , merlinofchaos suggested to use view booksmarks and I stumbled upon this module. Till then I never thought this was possible using views bookmark.
@dman as article explains there are drawbacks of using CCK for that. There may be workaround and I haven't explored those. One good example may be perhaps all records of a CCK type may not need this flag.
@quicksketch
I haven't given thought on how the UI will look on node summary or node view page. I was thinking more on the lines of
having a simple input field available in the node-edit form. This way a priviledged user can attach a metadata value to node. So using the same examples as in the article, instead of creating multiple booksmarks "featured,reviewed, highlighted" etc you can just create one bookmark which can have one of those ( or all of those) values. Or if there is a numeric value assigned (that is what I meant as nn; like 37) then a view can be created which has range of those values.
To simplify the input field may be available only inside the node-edit form and not on the readable page. But I admit, I haven't thought throught his.
Please note the CCK drawbacks or creating a new type drawbacks as mentioned in the article and why this module may be a better way. CCK is better suited for data which can be thought in advance and where the data attribute applies to all records in the dataset.
If you start thinking it is not a bookmarks system but way to attach metadata to nodes on demand(bookmarks is just one of the simplest implementation) then you can imagin the possibilities this can bring. It can become one of those must have module like CCK and views.
Comment #4
moshe weitzman commentedI think thats way out of scope for this module. For one, this module is typically used to provide user specific flags. i think you want global string values, but I am not sure. For global user specific flags, see community_tags module. Despite what that article says, I think CCK fields and taxonomy are good solutions for this, depending on the nature of your goal.
Comment #5
quicksketchAfter reading the article it looks like the idea to give nodes unspecified attributes is sort of tacked on there at the end. Views bookmark is the perfect solution for the article until about the last two paragraphs where drawk starts to talk about these attributes having any sort of value. Then it seems like he's starting to talk about something similar to free-tagging, but you can specify not only a tag but also the tag's value.
Earl mentioned views bookmark in the list of comments probably because it would solve the example in the article, not that it could be used as a system for assigning values to arbitrary attributes. This module was made to assign boolean flags (as Earl mentioned), I think that we should keep it confined to its intended purpose and freely assigning both attributes and values to nodes should be left up to a different (new?) module. tag_values.module anyone?
Comment #6
dman commentedStill totally off-topic for this module, but a good task. Where can we shift this thread to?
The objections to CCK are out-of-date. fields can be applied to any node type any time you like.
anyway, here's what I did last year when I wanted something like this (If I understand you):
Client was a parts store selling hardware, each of which had formal specifications, each of which had different types of spec. I certainly wasn't going to develop a hundred node types for them :-)
I wanted the type of attributes to be extendable, but still from a restricted list, so it's a selectbox hanging off a taxonomy. Both sides could be freetext fwiw, but that was'nt what I needed.
Attached module was only developed to the point where it would do what I wanted that month. No warrantee whatsoever, call it a proof of concept.
-----------------------
*************
** README: **
*************
DESCRIPTION:
-----------
This module provides a field type for cck that adds any number of user-defined fields.
Intented, for example, to extend a product catalog with structured
descriptions of size, weight, length, and other arbitrary specifications
where some products have them, and other have others - without requiring
a unique product type to be defined for every variation
REQUIREMENTS:
-------------
Requires the content.module to be installed.
USING THE MODULE:
------------------------
A details field should be associated with a new vocabulary,
which may define the appropriate terms that are then used as keys
that may be used to label the following fields.
To produce a result that displays
| Size: | 6cm
| Diameter: | 3.2cm
| Groove ID: |1/4"
on one item,and
| Size: | 6cm
| Length: | 2cm
| Angle: | 75'
on another, the field definition should be linked with a vocabulary
that contains the terms
[Size, Diameter, Groove ID, Length, Angle, ...]
That will then become available in the field edit widget as drop-down keys to choose from.
TODO:
-----
* Adding other widgets
Author:
-------
Dan Morrison
coders.co.nz
Credits:
-------
Built with reference to matrix.module
by Matthias Hutterer
Comment #7
quicksketchWow, dman that is hawt.
If this isn't a contributed module, it sure seems like it should be. The functionality is exactly what I'd figured we're talking about here, what fortune that you just so happen to be following this thread :)
Comment #8
quicksketchI'm closing this ticket with "by design", as Views Bookmark is meant to be (and will continue to be) a boolean based system.