mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-06-09 13:25:10 +02:00
Add notes for 2016-05-12
This commit is contained in:
parent
c7883cdd53
commit
fc3235ed84
GPG Key ID:
0FB860CC9C45B1B9
|
|
@ -102,3 +102,21 @@ fi
|
|||
- I've sent them a question about it
|
||||
- A user mentioned having problems with uploading a 33 MB PDF
|
||||
- I told her I would increase the limit temporarily tomorrow morning
|
||||
- Turns out she was able to decrease the size of the PDF so we didn't have to do anything
|
||||
|
||||
## 2016-05-12
|
||||
|
||||
- Looks like the issue that Abenet was having a few days ago with "Connection Reset" in Firefox might be due to a Firefox 46 issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1268775
|
||||
- I finally found a copy of the latest CG Core metadata guidelines and it looks like we can add a few more fields to our next migration:
|
||||
- dc.rplace.region → cg.coverage.region
|
||||
- dc.cplace.country → cg.coverage.country
|
||||
- Questions for CG people:
|
||||
- Our `dc.place` and `dc.srplace.subregion` could both map to `cg.coverage.admin-unit`?
|
||||
- Should we use `dc.contributor.crp` or `cg.contributor.crp` for the CRP (ours is `dc.crsubject.crpsubject`)?
|
||||
- Our `dc.contributor.affiliation` and `dc.contributor.corporate` could both map to `dc.contributor` and possibly `dc.contributor.center` depending on if it's a CG center or not
|
||||
- `dc.title.jtitle` could either map to `dc.publisher` or `dc.source` depending on how you read things
|
||||
- Found ~200 messed up CIAT values in `dc.publisher`:
|
||||
|
||||
```
|
||||
# select text_value from metadatavalue where resource_type_id=2 and metadata_field_id=39 and text_value similar to "% %";
|
||||
```
|
||||
|
|
|
|||
|
|
@ -196,8 +196,33 @@ fi
|
|||
<li>I’ve sent them a question about it</li>
|
||||
<li>A user mentioned having problems with uploading a 33 MB PDF</li>
|
||||
<li>I told her I would increase the limit temporarily tomorrow morning</li>
|
||||
<li>Turns out she was able to decrease the size of the PDF so we didn’t have to do anything</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-05-12:b7bf1a0f8f2415a40e1e11e343b04c0d">2016-05-12</h2>
|
||||
|
||||
<ul>
|
||||
<li>Looks like the issue that Abenet was having a few days ago with “Connection Reset” in Firefox might be due to a Firefox 46 issue: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1268775">https://bugzilla.mozilla.org/show_bug.cgi?id=1268775</a></li>
|
||||
<li>I finally found a copy of the latest CG Core metadata guidelines and it looks like we can add a few more fields to our next migration:
|
||||
|
||||
<ul>
|
||||
<li>dc.rplace.region → cg.coverage.region</li>
|
||||
<li>dc.cplace.country → cg.coverage.country</li>
|
||||
</ul></li>
|
||||
<li>Questions for CG people:
|
||||
|
||||
<ul>
|
||||
<li>Our <code>dc.place</code> and <code>dc.srplace.subregion</code> could both map to <code>cg.coverage.admin-unit</code>?</li>
|
||||
<li>Should we use <code>dc.contributor.crp</code> or <code>cg.contributor.crp</code> for the CRP (ours is <code>dc.crsubject.crpsubject</code>)?</li>
|
||||
<li>Our <code>dc.contributor.affiliation</code> and <code>dc.contributor.corporate</code> could both map to <code>dc.contributor</code> and possibly <code>dc.contributor.center</code> depending on if it’s a CG center or not</li>
|
||||
<li><code>dc.title.jtitle</code> could either map to <code>dc.publisher</code> or <code>dc.source</code> depending on how you read things</li>
|
||||
</ul></li>
|
||||
<li>Found ~200 messed up CIAT values in <code>dc.publisher</code>:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code># select text_value from metadatavalue where resource_type_id=2 and metadata_field_id=39 and text_value similar to "% %";
|
||||
</code></pre>
|
||||
|
||||
</section>
|
||||
<footer>
|
||||
|
||||
|
|
|
|||
|
|
@ -134,7 +134,32 @@ fi
|
|||
<li>I&rsquo;ve sent them a question about it</li>
|
||||
<li>A user mentioned having problems with uploading a 33 MB PDF</li>
|
||||
<li>I told her I would increase the limit temporarily tomorrow morning</li>
|
||||
<li>Turns out she was able to decrease the size of the PDF so we didn&rsquo;t have to do anything</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-05-12:b7bf1a0f8f2415a40e1e11e343b04c0d">2016-05-12</h2>
|
||||
|
||||
<ul>
|
||||
<li>Looks like the issue that Abenet was having a few days ago with &ldquo;Connection Reset&rdquo; in Firefox might be due to a Firefox 46 issue: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1268775">https://bugzilla.mozilla.org/show_bug.cgi?id=1268775</a></li>
|
||||
<li>I finally found a copy of the latest CG Core metadata guidelines and it looks like we can add a few more fields to our next migration:
|
||||
|
||||
<ul>
|
||||
<li>dc.rplace.region → cg.coverage.region</li>
|
||||
<li>dc.cplace.country → cg.coverage.country</li>
|
||||
</ul></li>
|
||||
<li>Questions for CG people:
|
||||
|
||||
<ul>
|
||||
<li>Our <code>dc.place</code> and <code>dc.srplace.subregion</code> could both map to <code>cg.coverage.admin-unit</code>?</li>
|
||||
<li>Should we use <code>dc.contributor.crp</code> or <code>cg.contributor.crp</code> for the CRP (ours is <code>dc.crsubject.crpsubject</code>)?</li>
|
||||
<li>Our <code>dc.contributor.affiliation</code> and <code>dc.contributor.corporate</code> could both map to <code>dc.contributor</code> and possibly <code>dc.contributor.center</code> depending on if it&rsquo;s a CG center or not</li>
|
||||
<li><code>dc.title.jtitle</code> could either map to <code>dc.publisher</code> or <code>dc.source</code> depending on how you read things</li>
|
||||
</ul></li>
|
||||
<li>Found ~200 messed up CIAT values in <code>dc.publisher</code>:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code># select text_value from metadatavalue where resource_type_id=2 and metadata_field_id=39 and text_value similar to &quot;% %&quot;;
|
||||
</code></pre>
|
||||
</description>
|
||||
</item>
|
||||
|
||||
|
|
|
|||
|
|
@ -134,7 +134,32 @@ fi
|
|||
<li>I&rsquo;ve sent them a question about it</li>
|
||||
<li>A user mentioned having problems with uploading a 33 MB PDF</li>
|
||||
<li>I told her I would increase the limit temporarily tomorrow morning</li>
|
||||
<li>Turns out she was able to decrease the size of the PDF so we didn&rsquo;t have to do anything</li>
|
||||
</ul>
|
||||
|
||||
<h2 id="2016-05-12:b7bf1a0f8f2415a40e1e11e343b04c0d">2016-05-12</h2>
|
||||
|
||||
<ul>
|
||||
<li>Looks like the issue that Abenet was having a few days ago with &ldquo;Connection Reset&rdquo; in Firefox might be due to a Firefox 46 issue: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1268775">https://bugzilla.mozilla.org/show_bug.cgi?id=1268775</a></li>
|
||||
<li>I finally found a copy of the latest CG Core metadata guidelines and it looks like we can add a few more fields to our next migration:
|
||||
|
||||
<ul>
|
||||
<li>dc.rplace.region → cg.coverage.region</li>
|
||||
<li>dc.cplace.country → cg.coverage.country</li>
|
||||
</ul></li>
|
||||
<li>Questions for CG people:
|
||||
|
||||
<ul>
|
||||
<li>Our <code>dc.place</code> and <code>dc.srplace.subregion</code> could both map to <code>cg.coverage.admin-unit</code>?</li>
|
||||
<li>Should we use <code>dc.contributor.crp</code> or <code>cg.contributor.crp</code> for the CRP (ours is <code>dc.crsubject.crpsubject</code>)?</li>
|
||||
<li>Our <code>dc.contributor.affiliation</code> and <code>dc.contributor.corporate</code> could both map to <code>dc.contributor</code> and possibly <code>dc.contributor.center</code> depending on if it&rsquo;s a CG center or not</li>
|
||||
<li><code>dc.title.jtitle</code> could either map to <code>dc.publisher</code> or <code>dc.source</code> depending on how you read things</li>
|
||||
</ul></li>
|
||||
<li>Found ~200 messed up CIAT values in <code>dc.publisher</code>:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code># select text_value from metadatavalue where resource_type_id=2 and metadata_field_id=39 and text_value similar to &quot;% %&quot;;
|
||||
</code></pre>
|
||||
</description>
|
||||
</item>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user