OAI ID in display

[patrickzurek]

JIRA issue created by: rcook Originally opened: 2011-12-15 06:39 PM

Issue body: (nt)

This issue has an attachment associated with it (external link): [OAI ID in display.png](http://www.carli.illinois.edu/sites/files/XCfiles/OAI ID in display.png)

[patrickzurek]

JIRA Comment by user: rcook JIRA Timestamp: 2011-12-15 06:43 PM

Comment body:

This comes from Judi Briden. She feels this info is not useful and distracting to a user. What are options for improving the look here?

[patrickzurek]

JIRA Comment by user: rcook JIRA Timestamp: 2011-12-15 09:34 PM

Comment body:

Peter made comment below in email. Also consider DRUPAL-210 which is to turn the right hand side off.

Yes, it is because we create highlight from the field which contains all information, including the OAI identifier. We might create a form which let admin to exclude some fields from this. Or we can create a workaround, which exclude some technical fields "hard wired" in the code.

[patrickzurek]

JIRA Comment by user: dlindahl JIRA Timestamp: 2011-12-20 05:39 PM

Comment body:

I just sent Peter a message about this. I will copy his comments here.

yes it is DT, which creates this "all in one" field. This contain all fields. Here is the code:

$content = ''; if (is_array($object->metadata)) { foreach ($object->metadata as $field => $values) { if (!isset($values) || empty($values) || !is_array($values)) { continue; } foreach ($values as $element_instance) { if (is_array($element_instance)) { foreach ($element_instance as $key => $value) { if ($key == '#value') { $content .= $value . ' '; } // foreach element_instances } } // foreach values else { // '@id', '@type' $content .= $element_instance . ' '; } } // processing arrays } } // processing metadata $document->addField('text', $content, FALSE, TRUE);

We have two options: 1) add some filters into it, and exclude some fields from this. This means that we won't able to search for eveything. You mention that no one wants to search for marctoxctransformation. That's true for end users, but it proved to be good, when you - as MST/DT developer or administrator - would like to debug, and wants to search for the technical fields, e.g. the OAI ID. But this use case I admit should not interferre with the general, end user's use case, so there is another solution

2) to keep the highlight and search separated - keep this field for search, and create another, that time the technical fields should be filtered out. We have to list the technical fields, which could be used here: OAI ID the uplink fields (xc:workExpressed, xc:expressionManifested, xc:manifestationHeld) I don't remember other, but we can later modify this list.

How does it sound for you? It is easy to implement (one hour work), and we can add other fields later, if needed. For testing what's in Solr, I have created a Solr-view, similar than schema view. It is not linked to anywhere, but the url is simple.

this is the scheme view: http://128.174.70.254/dtmilestone3/node/727904/xc/download

for the Solr view you have to replace the last element (download) to 'solr': http://128.174.70.254/dtmilestone3/node/727904/xc/solr

Péter

[patrickzurek]

JIRA Comment by user: dlindahl JIRA Timestamp: 2011-12-20 05:40 PM

Comment body:

I do not want to act on this now. A library is free to turn this feature off, or customize it to their liking. We might revisit later.

[patrickzurek]

JIRA Comment by user: pkiraly JIRA Timestamp: 2012-09-27 03:46 PM

Comment body:

It was resolved previously, no longer exists.

[patrickzurek]

Issue resolved: 2012-09-27 03:46 PM