Feature #6435
closed
ScholarPress COinS should support multiple values for some DC fields
Added by Boone Gorges over 7 years ago.
Updated over 6 years ago.
Category name:
WordPress Plugins
Description
Copying from https://redmine.gc.cuny.edu/issues/5490#change-26583:
Testing on http://jitpstaging.commons.gc.cuny.edu/city-of-lit-collaborative-research-in-literature-and-new-media/, I can confirm that the ScholarPress COinS translator kicks in as planned, and Zotero grabs whatever data is in the custom fields assigned by it. Thanks, Dan, for all your hard work on this plugin!
That said, unless I'm missing a way to trigger it, the plugin currently only allows for one author, with a single clear "last name" field. In the case of multiple authors, I tried a workaround of treating only the first author's last name as the requested "last name," and putting all other authors in the "first name" field, just to see what Zotero would do with it. Perhaps unsurprisingly, it treats this as a single author with a simple last name and a really complicated first name.
Don't get me wrong: it's still a vast improvement, and I'm grateful for it, and in many citation styles it'll probably even look right. But if there could be some way to make "author" a multi-valued array that Zotero could digest, that would be better still.
Dan, could you look into adding multi-tag support? Author is the one that's being requested above, but once you have an interface for that, it might make sense to use the same interface (rather than a comma-separated list) for Subject. Are there other tags that should allow multiple values?
- Related to Feature #5490: Ability to embed DC or COinS metadata added
Author's the main one, though Zotero also allows multiple categories of creator: Contributor, Editor, etc, if we want to generalize beyond our specific use-case.
Also, I didn't realize it until going in to check for those creator types, but we're also currently passing "Web Site" as the Item Type; might that also be settable in the plugin? In our case, "Journal Article" would be more on target. That's probably a different issue, though.
Dear Boone and Dan,
I just wanted to check in on this issue to see what your anticipated timeline is for multi-author support on the COinS plugin. The new issue of JITP should be ready to launch some time next week, so of course that would be ideal for us, but I know you both have many other things going on. If this is impossible for now, I'll go ahead with the kludge for multiple authors of treating secondary authors as a complex first name for the primary author.
All best, and gratefully,
Ben
Hi Ben - I'm afraid it's quite unlikely that anything will be available by next week. It's possible that we'll have something within the next month or so. Please do watch for updates from this ticket, and we'll let you know when there's something to test.
I totally get it, and thanks for confirming. As I said up front, even with only one author field, this is already a major improvement, and we're happy to have it!
- Target version changed from 1.11 to 1.12
Hi Dan - A quick ping on this. Any thoughts about whether it'd be hard to implement? It could be a relatively easy win, if you can leverage an existing multiple-values interface. (Maybe you can repurpose some logic from the group social media selectors?)
- Target version changed from 1.12 to 1.13
This would be nice to include, but I'd prefer to focus efforts on #8639.
Functionality generally looks good to me. I never would have thought to store all last names together and all first names together, instead of as pairs, but it seems to work :)
I pushed up a couple changes related to internationalization. Once you've had a review, I think we're good for a release. We could probably sneak these improvements into a minor release if they come as part of a public scholarpress-coins update.
Yeah - I'm not sure if it's guaranteed to always work on PHP's end, but I haven't had any issues yet. It just makes it much easier to send and parse the data between the post edit screen, the data base, and the front end, and greatly simplifies the javascript for adding and removing the fieldsets.
Those changes look good - thank you Boone! I also addressed some of the other lingering issues raised in the GitHub repo. Should I go ahead and do a public update for the Wordpress plugin directory?
- Target version changed from 1.13 to 1.12.1
Yup, go ahead and push it out. Thanks, Dan!
Great! I've gone ahead and brought it up to 2.2 in the plugin directory.
- Status changed from Assigned to Resolved
Also available in: Atom
PDF