Dear David,

Thank you for the CSL specification link. I read in the specification about 
the property container-title which says: 


> *container-title*Title of the container holding the item (e.g. the book 
> title for a book chapter, the *journal title* for a journal article; the 
> album title for a recording; the session title for multi-part presentation 
> at a conference)


Since the properties found in csl-citation.xml are not repeatable, I cannot 
assign the metadata for the journal-title because I already mapped it to 
the metadata for the book title. If I map the journal-title to the property 
journalAbbreviation, it is not picked up by the citation generator. I don't 
know how https://oskar-bordeaux.fr/ managed to map their metadata since 
their repository has also mixed types like journal articles and book 
chapters.

I would love to hear from others in the list who have applied the CSL patch 
and how they map their metadata to the existing properties in the 
csl-citation.xml.

Thanks in advance and best regards,
Euler

On Thursday, July 9, 2020 at 10:38:39 PM UTC+8, David Cavrenne wrote:
>
> Dear Euler,
>
> Thank you for your interest in the CSL patch !
>
> Defining the metadata mappings in csl-citation.xml is indeed not an easy 
> task. We have just added a link to the CSL specification (i.e. 
> https://github.com/citation-style-language/documentation/blob/master/specification.rst)
>  
> in our patch documentation, hoping to provide some guidance about this.
> There is specific information in the above documentation which might be 
> useful for the specific use case that you reported:
>
> *If a container-title is present, the item is interpreted as a book 
> republished in a collection or anthology;*
>
> *Also used for whole conference proceedings volumes or exhibition catalogs 
> by specifying event and related variables*
>
>
> Regarding your second question, the idea of combining/transforming 
> different metadata fields is a really interesting use case, thanks for 
> that. This was not in our original scope, but I’m sure that if someone 
> would be willing to fund this, University of Bordeaux could accept a pull 
> request for this work.
>
> Thanks again for installing the CSL patch on your repository !
> Best regards,
>
> David
>
> On Wednesday, July 1, 2020 at 4:29:26 PM UTC+2, esnemiz wrote:
>>
>> Dear Bram,
>>
>> First of all, thanks to Atmire and the University of Bordeaux for 
>> providing a free and open-source patch that allowed exporting of items in 
>> different citation styles. We have implemented it already in our 
>> institutional repository since we find it very useful.
>>
>> I would like to ask for clarifications though, with regards to the 
>> mapping of metadata in the configuration file csl-citation.xml. Since 
>> our repository mostly contains journal articles and conference papers, we 
>> must include the source (eg Journal title, Book title, Conference 
>> proceedings title) in the generated citation. I figured out that for the 
>> book title of an item with a book chapter type, it is the property named "
>> containerTitle" after numerous trial and error. I can't figure out what 
>> property should I map the title of the proceedings for items with type 
>> conference paper and the journal-title for items with type article, 
>> magazine article, and newspaper article. If I map the journal-title to the 
>> property named "containerTitle", it is displaying the word "In" eg 
>> *Primavera, 
>> J. H. (2006). Overcoming the impacts of aquaculture on the coastal zone 
>> [Article]. In Ocean and Coastal Management (Vol. 49, Issues 9–10)* 
>> instead of *Primavera, J. H. (2006). Overcoming the impacts of 
>> aquaculture on the coastal zone. **Ocean and Coastal 
>> Management, 49(9-10)* using the APA citation style for example.
>>
>> Another thing is about page numbers. Some of our custom meta-tags were 
>> based on the recommendation of Google scholar (
>> https://scholar.google.com/intl/en/scholar/inclusion.html#indexing). So 
>> we only have "citation_firstpage" and "citation_lastpage" and we don't have 
>> the pages or page-range metadata. Is there a way to reuse the values found 
>> in citation_firstpage and citation_lastpage for the page range property 
>> without having to create a new metadata field for page range?
>>
>> I hope my questions can be resolved without modifying the java code.
>>
>> Thanks again and best regards,
>> Euler
>>
>> On Friday, June 12, 2020, at 9:46:39 PM UTC+8, Bram Luyten wrote:
>>>
>>> Hello friends,
>>>
>>> Thanks to funding from the University of Bordeaux, we were able to 
>>> create and release a patch for DSpace 6 XMLUI, adding 
>>> https://citationstyles.org/ export support.
>>>
>>> Learn more:
>>> https://bit.ly/csl-patch-generallist
>>>
>>> have a nice weekend!!!
>>>
>>> Bram
>>>
>>> [image: logo] Bram Luyten
>>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
>>> Gaston Geenslaan 14, 3001 Leuven, Belgium
>>> DSpace Express Hosting 
>>> <https://www.atmire.com/dspace-express?utm_source=emailfooter&utm_medium=email&utm_campaign=braml>
>>>  - Open Repository Hosting 
>>> <https://www.atmire.com/open-repository?utm_source=emailfooter&utm_medium=email&utm_campaign=braml>
>>>  - Custom DSpace Services 
>>> <https://www.atmire.com/custom-dspace?utm_source=emailfooter&utm_medium=email&utm_campaign=braml>
>>>
>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ee097070-57f2-4c66-8502-e8c13504735co%40googlegroups.com.

Reply via email to