[D7 Port] Customising the vocabulary hosting page

Lin, I have the current latest patch at http://drupal.org/node/1196510#comment-4696374
It does assign url aliases for vocabulary.
I will check out the Render example asap!

For reference, this is a list of fields which is currently being displayed on the workspace page and the list of fields/links that are additionally needed there :

Fields currently showing :

1. Name of the workspace/Main vocabulary : as the title on the page
2. Authors of the workspace
3. Namespace URI / Vocabulary ID: in the address bar as the alias

Fields/ Buttons required additionally :

1. Displaying the main vocabualry information:

- abstract
- body
- additional custom RDF

2. Links/Buttons to add class and property.
3. Links/Buttons to enable content negotiation.

Once the class and property fields are added, we also need to show :

• All the classes in the vocabulary
• All the properties in the vocabulary

Later on, we also need to put buttons to import external vocabularies to the workspace, and then display them as links on the page.

I have been trying to get the Add class and Add property links on the vocabulary workspace page. I have tried out two methods for that -

1. Using Render Arrays - Failed
Initially I thought of adding add-class and add-property links on the navigation menu which contains the View, Edit and RDF links. I used hook_page_alter() and tried to dig deep into the array structure and locate these items. However, the code for that particular navigation is not appearing in the $page which is passed to hook_page_alter() and instead, it simply renders a predefined navigation in the code. So I cant modify that menu and add new links.

2. Using Field Collections - Working
I tried to add field collections to the vocabulary workspace page through the UI, and it does provide an add link to the vocabulary workspace and it looks good for our purpose.
However, while saving the field collection, I would need to create a class/property node as well, so I will have to probably hack into the function which saves the class and property and save the class node, so I would need some more time for that. What do you think ?

I can roll a patch which provides add-class and add-property links on the workspace page without actually creating the nodes in the backend for now. Should I do that ?

Also, should I continue to use the Field collections (which adds 2 more dependencies for Neologism, ie, Entities API and Field collection module) or are there any more ways that I should explore ?

Another problem that I am facing is in defining links in hook_menu(). I was trying to define links of the type $items['node/%neologism_vocabulary/add-class'], which is expected to return render the class_node_form(). The drupal-6 code for the same is not working anymore, and some other ways I tried also didnt work. However, I will try to look deeper into this and get it working.

The hook_menu() method for displaying Add class/property links is working.

Add class and Add property links are available on the main Vocabulary node page at the moment, and a link to the main vocabulary node page is available on the vocabulary workspace for now.

In the Class and Property node forms, the 'Related Vocabulary' fields are hidden from the users now. When we save a class/property, the 'Related Vocabulary' field is automatically populated in the backend, and the link between vocabulary and class/property is created.

So now we have a link from vocabulary workspace to main vocabulary and from main vocabulary to its classes and properties.

However, whevener we save the class/property, the following notice pops up :

Notice: Only variable references should be returned by reference in neologism_vocabulary_load() (line 78 of ../neologism.module).

This is probably because we are returning FALSE in the following two condition inside the module neologism_load()

function &neologism_vocabulary_load($nid) {
  if (!$nid) return false;
  $node = node_load($nid);
  if (!$node || $node->type != 'vocabulary') return false;
  return $node;
}

Trying to get rid of this pop up notice now.

Patch for displaying add-class and add-property links on vocabulary node page.

Known issues :

1. Menu system is heavily cached so one may need to 'Clear all caches' just once after applying the patch
(Configuration » Development » Performance -> Clear all caches). After this, the add-class and add-property links appear on vocabulary page.

2. The Notice mentioned in the above comment still pops up on saving class/property.

I reopened the issue since there is bit of work still left here :)

I have figured out a way to dynamically update the vocabulary overview page, but there is a problem with my approach.

I plan to use hook_node_insert() which would be invoked each time a node is added. I would then check if the node type is class /property and then update the body of the vocabulary workspace using the $node parameter which is passed to the hook function.

However, the problem here is data duplication. If the user decides to edit the class/property, then there might be issues. We can use hook_node_update() which respond to updates to a node, but there might be a lot of loopholes this way.

Any suggestions ?

I think i figured out a way to correctly handle the data duplication. The data will be added to the vocabulary overview page as follows :

1. Install two fields in the vocabulary workspace entity:

• workspace_property_space
• workspace_class_space

2. Set display settings such that it is hidden in teaser mode and visible in default mode.

3. Set the '#access' attribute to false to hide these fields from the users while the vocabulary workspace form is presented.

$form['workspace_vocabulary_space']['#access'] = FALSE;

Thus, these fields will not be visible to the users but we can dynamically populate them and make them visible on the vocabulary workspace page.

4. The links to add class and property already appear on the vocabulary node page. Add new class/property through these.

5. Define hook_node_insert() which accepts $node parameter and is invoked whenever a new node is created.

6. Inside hook_node_insert(), check if the $node->type is class/property.

7. If it is class/property, then get the id of the vocabulary to which it is associated using

$vocabulary_nid = $node->vocabulary->nid;

8. Use the 'nid' of vocabulary to get the 'nid' of the related Vocabulary workspace node, using

$query = "SELECT field_data_workspace_main_vocabulary.entity_id FROM field_data_workspace_main_vocabulary WHERE field_data_workspace_main_vocabulary.workspace_main_vocabulary_nid  ='" . $vocabulary_nid . "';";

$table_attribute_value_array = db_query($query)->fetchCol();

$vocabulary_workspace_nid = $table_attribute_value_array[0];        

9. Load the vocabulary workspace node

$vocabulary_workspace_node = node_load($vocabulary_workspace_nid);

10. Edit the workspace_class_space/workspace_property_space field of this node, whichever is appropriate.

$vocabulary_workspace_node->workspace_class_space['und']['0']['value'] = "  div... id=$node->nid ... [add whatever class data we want to add here] ... "

Here, each new entry will be added in a div which will have the id equal to node id of the class/property so that it can later be identified and updated when the user wants to make changes. When the user makes changes to already existing class/properties, then we will use hook_node_update(), which respond to updates to a node.

11. Save the vocabulary workspace node.

node_save($vocabulary_workspace_node);

Hope I make some sense here :) Data duplication is unavoidable but hopefully this should be able to correctly handle it during insert/update.

This is a Great way ! Working on the patch.

I wrote down a crude code for testing out the method and it seems to work fine except that i haven't yet figured out where to append the render arrays on the workspace page. At the moment, the classes are prepended to the page, i.e. they appear before all the other stuff in $node->content. I will need to figure out the page structure and place the

// inside function neologism_node_view($node, $view_mode)
 ...
   if($node->type == 'workspace'){

        $main_vocabulary_id = $node->workspace_main_vocabulary['und']['0']['nid'];
        
        $query = new EntityFieldQuery();

        // displaying main vocabulary classes
        $entities = $query->entityCondition('entity_type', 'node')
                          ->entityCondition('bundle', 'class')
                          ->propertyCondition('status', 1)
                          ->fieldCondition('class_related_vocabulary', 'nid' , $main_vocabulary_id, '=')
                          ->execute();

        if(!empty($entities)){
            $nodes = node_load_multiple(array_keys($entities['node']));
            $views = node_view_multiple($nodes, 'teaser');
            $node->content += $views['nodes']; // change this
        }
   }
...

Patch for adding class and property info. on the workspace without data duplication.
Weights were employed to place the data properly.

Suspending the remaining part of issue for now in the interest of time and working on RDF output.

TODO:
1. Create custom view mode.
2. Creating headings separating class and property.
3. Should we add more information about the Main vocabulary on the workspace page?

I had created a custom view mode before so if I get the time I would try to work on that.

For creating headings which say "Main vocabulary Classes" and "Main vocabulary Properties" on the Workspace page, I tried to use the #title attribute (just like I have used the #weight attribute) but it didnt work out.

Development switched to #1242076: [D7 Port] Port the RDF output to D7

The workspace looks much better now with this patch.

Patch fixing following bugs :

1. Added links to the workspace to :

• Add Class to Main Vocabulary (functional)
• Add Property to Main Vocabulary (functional)
• RDF/XML output (not functional atm)

2. Added headings Main Vocabulary Classes and Main Vocabulary Properties separating class and property.

3. In the Add-class and Add-property forms, the prefix for URI now appears correctly populated with the vocabulary-id :
eg. http://.../foaf# instead of http://.../vocabulary-id#

Also, shouldn't we remove the rdfx dependency from .info file ?

fixed