Ticket #690 (new enhancement)

Opened 1 year ago

Last modified 9 months ago

pull image attribution info from the cover image article and display on TOC page

Reported by: russ Assigned to: rich
Priority: high Milestone:
Component: ambra Version: 0.8
Keywords: Cc:
Blocking: Blocked By:

Description

There's a placeholder on the TOC page that reads "Image Credit: Credit information goes here."

This should be pulling the data that's currently in the <attrib> field in the cover article xml. If that's hard, we can change the xml to accomodate...if that's impossible for 0.8.1 we can hard code credit info into the description xml. 

      <sec id="s1">
        <fig id="issue-pntd-image-v1-i1-g001">
            <object-id pub-id-type="doi">10.1371/issue.pntd.image.v1.i1.g001</object-id>
                <caption>
                  <title>Hope</title>
                   <p>Emma Burns is a science illustrator who uses traditional and digital media to create images that depict a st\
ory or convey meaning with a single glance. A passionate interest in both biology and the arts led her to a combination of the two\
 professions, wherein she creates artwork that reflects the scientific realm. Along with her lifelong interest in art, Emma earned\
 a degree in Biology from the University of York. Inspired by the knowledge she gained, she set sail for California, where she too\
k a graduate program in Science Illustration. She is fascinated by the natural world, and flora and fauna are commonly found in he\
r illustrations. Emma feels that it is important to use art to depict global health issues and articulate them in a way that draws\
 the attention of the general public.</p>
                </caption>
             <graphic xlink:href="issue.pntd.image.v1.i1.g001.tif"></graphic>
            <attrib>by Emma Burns</attrib>
            <copyright-statement>&copy; 2007 Emma Burns.</copyright-statement>
            </fig>
      </sec>

Dependency Graph

Change History

10/12/07 15:18:19 changed by russ

  • priority changed from critical to high.

this is not a block.

11/08/07 17:37:38 changed by rich

  • owner changed from jsuttor to alex.
  • milestone set to 0.8.2.

12/03/07 15:47:18 changed by rich

  • owner changed from alex to russ.

Russ to take first pass with XSL

12/14/07 09:32:45 changed by rich

  • milestone changed from 0.8.2 to pubApp_0.8.3.

12/17/07 17:56:22 changed by rich

  • milestone deleted.

12/27/07 16:51:40 changed by russ

  • status changed from new to assigned.

02/19/08 14:48:19 changed by rich

Comments from Alex

I assume you need a list of these files for the purpose of resolving ticket #690, since that is in the subject line of your email. I have looked into this today but I’m really out of my depth on the XSL transformations – I hope this is where the XSL contractor’s skill are stronger. Perhaps Jeff can help in that area. If not, we’ll have to go back to the topaz team (Pradeep, Ronald, Amit) who originally put this stuff together.

BrowseIssue? page (TOC?)

FTL: src\plos\webapp\src\main\webapp\article\browseIssue.ftl

Action: src\plos\webapp\src\main\java\org\plos\article\action\BrowseIssueAction?.java

The issue description is provided to the browseIssue.ftl by the BrowseIssueAction? via the ‘issueDescription’ bean property. I actually don’t see the placeholder described in #690 in the browseIssue.ftl page, but if we want to add this, then we should introduce a new bean property with the image attribution description and expose it to the ftl via getter/setter methods.

The image attribution needs to be pulled from the “imageArticle” referenced by the IssueInfo? domain object. We should pull out the image attribution information when we build the Issue domain object. An immediate workaround for this would be to allow this information to be entered on the admin page when the issue is created. The next step should be to populate this field automatically from the article – it seems more useful to automatically populate the field and then allow the administrator to alter it if desired.

I’m not sure that we actually pull the image <attrib> information from the original article XML. It’s achieved via XSL transformations on article ingestion. I’ve been digging into this toady and I can see that Ingester.zip2Obj() transforms the article zip file into a Document using the pmc2obj.xslt handler – I don’t understand the insides of that handler however.

I also don’t see a placeholder in the DublinCore? for the image <attrib> information. This is where the article description is stored. I’m not sure that we would want to store this information for every article. Is it a standard?

Ingester.mulgaraInsert() finds all RDF statements in the Document returned from zip2Obj() and inserts an triple for each RDF statement found.

To implement this correctly I assume we need to extend DublinCore? to accommodate the image <attrib> information – or reuse another existing element in the case of the “Image Article”. Since these are core changes to the data, we should discuss this with the topaz team.

03/06/08 17:16:08 changed by russ

  • owner changed from russ to rich.
  • status changed from assigned to new.