diff --git a/content/post/2017-07.md b/content/post/2017-07.md index bdb762485..f3cd7844f 100644 --- a/content/post/2017-07.md +++ b/content/post/2017-07.md @@ -31,3 +31,4 @@ $ psql dspacenew -x -c 'select element, qualifier, scope_note from metadatafield - We also need to check to see which ORCID authority core this uses, because it seems to be using an entirely new one rather than the one for `dc.contributor.author` (which makes sense of course, but fuck, all the author problems aren't bad enough?!) - Also would need to edit XMLUI item displays to incorporate this into authors list - And fuck, then anyone consuming our data via REST / OAI will not notice that we have an author outside of `dc.contributor.authors`... ugh +- What if we modify the item submission form to use [`type-bind` fields to show/hide certain fields depending on the type](https://wiki.duraspace.org/display/DSDOC5x/Submission+User+Interface#SubmissionUserInterface-ItemtypeBasedMetadataCollection)? diff --git a/public/2017-07/index.html b/public/2017-07/index.html index 15040059b..6461fb32f 100644 --- a/public/2017-07/index.html +++ b/public/2017-07/index.html @@ -27,7 +27,7 @@ We can use PostgreSQL’s extended output format (-x) plus sed to format the - + @@ -73,9 +73,9 @@ We can use PostgreSQL’s extended output format (-x) plus sed to format the "@type": "BlogPosting", "headline": "July, 2017", "url": "https://alanorth.github.io/cgspace-notes/2017-07/", - "wordCount": "232", + "wordCount": "252", "datePublished": "2017-07-01T18:03:52+03:00", - "dateModified": "2017-07-04T10:53:39+03:00", + "dateModified": "2017-07-04T13:49:16+03:00", "author": { "@type": "Person", "name": "Alan Orth" @@ -170,6 +170,7 @@ We can use PostgreSQL’s extended output format (-x) plus sed to format the
dc.contributor.author
(which makes sense of course, but fuck, all the author problems aren’t bad enough?!)dc.contributor.authors
… ughtype-bind
fields to show/hide certain fields depending on the type?