taxonomy

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
kvantomme's picture

CCK versus Taxonomy for node referencing

I had been looking for a way to have a two-way reference between 2 nodes. You would need this for basic CRM functionality e.g. to be able to link a person to a company or an action to a project. This way you can go to a person and see what company he is part of or go to that company and see all the people that are working in that company.

Read more
Marcus VBP's picture

Mostra a contribuição mais recente de uma taxonomy

Tudo bom pessoal?

Gostaria de saber como listar apenas o artigo mais recente de uma determinada Taxonomy, em um bloco. A aparência deve ser exatamente como um teaser de artigo na página inicial, ou seja, tem que ter título, o "enviado por", o teaser, e os links depois do teaser.

Alguém pode me ajudar com isso?

Read more
mlncn's picture

Community-managed Categories

(Submitted at five seconds of the deadline!)

<

blockquote>Abstract: I will introduce several features to enable communities of users to create and manage categories directly. Users will be able to vote to combine terms or to move terms under one another in a hierarchy.

Read more
Senpai's picture

Is there a way to see all the taxo terms of a group?

I've been trying to find a way to coax a listing of all taxonomy terms for g.d.o groups. Thus far, it has been in vain. Do any of you know how this might be achieved without writing a module, or patching core? The top-10 list at the right side of a group is just not enough info for a group admin to keep things streamlined and organized.

Ideas? Sogg-gestions?

[/Senpai]

Might this be a help? http://drupal.org/node/16489

Read more
TheOverclocked's picture

Can't edit my vocabulary terms

I recently started the group vBulletin and I accidentally added a term I which I no longer need. When I try to edit any of my terms I just get an error that I'm not authorized to view the page.

Am I missing something somewhere that allows me to do that?

Read more
bradwade's picture

Church Taxonomy Examples

I am wondering what an effective taxonomy for churches would be (and if there is a common taxonomy among churches). What taxonomy structure are you using for you church's drupal site?

Read more
Rosamunda's picture

Completely lost

Hi there!
I´ve been searching the forums for a while, and I´m sincerely lost about this issue.

I came to realize that there´s NO WAY to add taxonomy terms to the simple, yet easy, core module "profile".

So, I´ve installed the nodeprofile module. It needs the nodefamily to run, and it suggests you to install the usernode module.
I´ve done all that, and I´ve readed the readme files of all of them.

And yet, I´m clueless about how to replace the profile with all this confusing stuff. I´ve installed three modules already to replace one.

Read more
consen's picture

Practical demonstration of Drupal (rich info-Space) on IST-2006 21/23 November Helsinki (FIN)

Start: 
2006-11-21 09:00 - 2006-11-23 10:28 Europe/Helsinki

IST-2006 21/23 November Helsinki (FIN) open invitation to collaborate in IST-Media-Blog Exhibition

The European Commission (EC) DG Information Society has approved the exhibition in the IST-2006 21/23 November Helsinki (FIN) of
http://ec.europa.eu/information_society/istevent/2006/index_en.htm

IST-Media-Blog (Rich media profiles for all) Cordis 3rd generation.

http://IST-2006.consen.info/

CONSEN Euro-Group, DrupalCat and MUFICATA-ZENSCI offer you (Drupal community and professionals) the opportunity of co-organize this exhibition in a Practical, Integrative, Cooperative, Demonstrative, Scientific, technologic and Business innovative effort to build a web-portal, database and a sustainable and responsible socio-economic exploitable Info-Space.

Read more
robertDouglass's picture

Reposts of Grugnog's proposals - Relationships API

  • Standard set of hooks to allow modules to express relationships and query them
  • Requirements (based on discussions at OSCMS Vancouver 2006):
    • Pluggable frontends (ways of entering and viewing relationships). Experience has shown that there are many different ways relationships can be created and presented to users. See the 'Relationship UI' child page for a simple frontend.
    • Pluggable backends (ways of storing/retrieving or deriving relationship data). Experience has shown that some modules will need direct control of the relationship storage space. See the 'Network Relationships', 'Hierachical Relationships' and 'CiviCRM Relationships' child pages for example backends.
    • Extensible
    • Works with both 1-1 and 1-many relationships
    • Object neutral - can relate nodes, users, comments, relationships, URIs
    • Can retrieve direct relationships (e.g. friend - L1) as well as as indirect relationships (e.g. friend-of-a-friend - L2, friend-of-a-friend-of-a-friend - L3 etc)
    • Can retrieve relationships taking into account direction (e.g. only parents or only children) or ignoring direction (e.g. relatives)

    Additional requirements for discussion:

    • Each relationship type can be a node - easily extensible with metadata explaining what this relationship 'means'. Additionally - or alternatively - we could allow a simple keyword to define the relationship type.
    • Split off the API from the 'standard' backends and frontend to make it easier to maintain and add to core.
    • Direct (L1) relationships could be cached with the node - we could even 'grow' the node relationship cache for higher level relationships as they are requested, possibly with certain limits.
    • Relationships can be directional or non-directional - we could track this with the relationship type (i.e. if the relationship type has an 'inverse' then it is directional).
  • Potential use cases for relationships in Drupal
    • Node authorship (multiple authors!)
    • Taxonomy (which is relating to a point in a taxonomy tree, which can also be created using relationships)
    • Media or other attachments to a node
    • Web Links (relating to an external URI) - these could optionally be picked up from the node body and/or tracked using weblinks.module
    • Event and volunteer signups
    • Comment threading
    • Metadata in general
    • Tracking users buddies
    • Tracking user content likes/dislikes
    • Adding AI-like capabilities 'If you liked this, you'll love...'
    • Lastly, but certainly not least - the semantic web (RDF, FOAF...) revolution!
  • Potential DEP Dependencies:
    • Users, comments, taxonomy terms and attachments become nodes. Without this DEP the RAPI would be significantly more complex, because of the need for either a table mapping 'object-ids' to node, comment and user ids, or tracking the tables in question directly with each relationship
Read more
Subscribe with RSS Syndicate content