Ticket #704 (closed enhancement: fixed)

Opened 1 year ago

Last modified 5 months ago

configurable plos article type list

Reported by: russ Assigned to: alex
Priority: high Milestone:
Component: ambra Version: 0.8.1
Keywords: article type Cc:
Blocking: Blocked By:

Description

we should store the list of plos article types in mulgara, so that it's easy to retrieve the plos article type from mulgara when building articles, browse pages, etc.

multiple article types are applied to an article on ingest. here's a typical set of triples for an article: 

    <solution>
      <s resource="info:doi/10.1371/journal.pone.0000545"/>
      <p resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#type"/> [^]
      <o resource="http://rdf.topazproject.org/RDF/Article"/> [^]
    </solution>
    <solution>
      <s resource="info:doi/10.1371/journal.pone.0000545"/>
      <p resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#type"/> [^]
      <o resource="http://rdf.plos.org/RDF/articleType/research-article"/> [^]
    </solution>
    <solution>
      <s resource="info:doi/10.1371/journal.pone.0000545"/>
      <p resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#type"/> [^]
      <o resource="http://rdf.plos.org/RDF/articleType/Research%20Article"/> [^]
    </solution>
  • rdf.topazproject.org/RDF/Article is part of the topaz model
  • rdf.plos.org/RDF/articleType/research-article is the PMC article type
  • rdf.plos.org/RDF/articleType/Research%20Article is the PLoS article type, which we actually want to display on the article page and else on the web sites.

The proposed solution is to insert triples into mulgara that create a PLoS Article class with all of the PLoS article strings as members.

Ideally this list would exist in the pub apps config files, and would be instantiated in Mulgara on start up.

Changes will need to be made to Article.java, and we'll need a new PLoSArticleType.java to reflect the changes to the model.

Dependency Graph

Change History

10/29/07 14:06:09 changed by russ

  • version set to 0.8.1.

11/08/07 12:46:28 changed by alex

Does anyone have suggestions for where the article types should be defined? Should this be in a new section in the defaults.xml config file?

11/08/07 12:54:05 changed by amit

See my email... But for historical purposes, I will state it here also. Why is this needed now? If the article type display order is implicitly coded in the presentation layer and the fact that you can fetch all the article-types associated with an article, does the information need to be repeated?

11/08/07 13:24:10 changed by amit

Please see r4049. My cursory read is that the hard coding of the article-types was removed (the original purpose of this ticket).

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

  • summary changed from store plos article type list in mulgara to configurable plos article type list in mulgara.

11/09/07 13:51:27 changed by russ

  • summary changed from configurable plos article type list in mulgara to configurable plos article type list.

changing title - we're on the fence about whether the list should live in mulgara or java

11/24/07 14:51:32 changed by alex

(In [4105]) re #704 - Merged configurable article types from head

11/27/07 12:34:26 changed by alex

  • status changed from new to closed.
  • resolution set to fixed.

I've added the ability to define an ordered list of Article Types in defaults.xml. Please see the <articleTypeList> element section for an example. The article types listed here will be used in this order on the TOC page. Any article defined in the mulgara as:

<article-doi> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <article-type-doi>

where the <article-type-doi> matches the article type defined in defaults.xml

Note that the article-type triple in Mulgara is defined when the article is ingested and is derived from either of:

* the top level attribute defined in the <article article-type="..."> element * the content of the element matching <article-categories><subj-group subj-group-type="heading"><subject>...</subject></subj-group></article-categories>

In either case, the prefix "http://rdf.plos.org/RDF/articleType/" is added to the article type. In the second case, the article type is URL encoded (i.e. spaces become %20).

12/19/07 12:42:30 changed by russ

  • status changed from closed to reopened.
  • resolution deleted.

12/19/07 13:00:56 changed by russ

it looks like the old solution for this - a hard coded article type list in FetchArticleAction?.java and elsewhere - still exists and it should be removed now that we're defining the list in config.

i think this is the case because the 'Issue Image' article i ingested on plosone-branch is showing 'Issue Image' as it's articleTypeHeading even though i don't have an issue image defined in config.

i also tried to override the issue image typeHeading in config, and that didn't work.

maybe we never made it clear that fetchArticle should also respect the article type list in config?

if fetchArticle is hard, we can probably open a new ticket for it in the next milestone...

(follow-up: ↓ 12 ) 12/19/07 13:21:55 changed by russ

another related issue:

there are some article types that we don't want to appear on the browseIssue page in the article list, namely Issue Image (which is displayed at the top of browseIssue through a different method i guess).

could we add an element or attribute to <articleType> that can be used to suppress that type from the browseIssue page article list?

eg: 

	<articleType>
		<typeUri>http://rdf.plos.org/RDF/articleType/Issue%20Image</typeUri>
		<typeHeading>Issue Image</typeHeading>
		<imageSetConfigName>coverImage</imageSetConfigName>
                <browseable>false</browseable>
	</articleType>

(in reply to: ↑ 11 ) 12/19/07 16:51:55 changed by russ

Replying to russ:

another related issue: there are some article types that we don't want to appear on the browseIssue page in the article list, namely Issue Image (which is displayed at the top of browseIssue through a different method i guess).

I'm being stupid. There's no reason to add the issue image to the issue. therefore, there's no need to specifically exclude it from the article list.

12/21/07 14:38:37 changed by russ

tested, confirmed (fetchArticle.action respects config article type list)

12/21/07 14:38:49 changed by russ

  • status changed from reopened to closed.
  • resolution set to fixed.

01/02/08 13:11:44 changed by jsuttor

(In [4291]) Recorded merge of revisions 4105 via svnmerge from http://gandalf.topazproject.org/svn/branches/0.8.2

........

r4105 | alex | 2007-11-24 14:51:32 -0800 (Sat, 24 Nov 2007) | 1 line

re #704 - Merged configurable article types from head

........

07/16/08 11:01:46 changed by

  • milestone deleted.

Milestone 0.8.2 deleted