Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362017-10-24T16:56:55ZEcoinformatics Redmine
Redmine Feature #7222 (New): In the EML .xslts, take the "id" attribute set on entity elements (e.g. othe...https://projects.ecoinformatics.org/ecoinfo/issues/72222017-10-24T16:56:55ZLauren Walkerwalker@nceas.ucsb.edu
<p>The identifiers should be taken from the `id` attribute set on the root entity element, e.g. `otherEntity` or `dataTable`, and put them in a `data-pid` attribute set on the entitydetails div. MetacatUI uses this attribute as the primary location for matching data objects with entitydetails sections.</p> Feature #7209 (New): Support for XSL transform of iso19115 metadata formathttps://projects.ecoinformatics.org/ecoinfo/issues/72092017-09-08T17:53:56ZJing Taotao@nceas.ucsb.edu
<p>Details see <a class="external" href="https://redmine.dataone.org/issues/7754">https://redmine.dataone.org/issues/7754</a></p> Feature #7198 (New): Format solr engine description outputhttps://projects.ecoinformatics.org/ecoinfo/issues/71982017-06-02T17:30:11ZPeter Slaughterslaughter@nceas.ucsb.edu
<p>The solr engine description information from DataONE has XSLT formatted output that includes a description of each field: <a class="external" href="https://cn.dataone.org/cn/v2/query/solr">https://cn.dataone.org/cn/v2/query/solr</a>. The corresponding metacat index output does not: <a class="external" href="https://knb.ecoinformatics.org/knb/d1/mn/v2/query/solr">https://knb.ecoinformatics.org/knb/d1/mn/v2/query/solr</a>. It would be very useful to provide users with this info to help them use/learn solr and our index.<br />I wasn't able to find the .xsl file in metacat repo or the DataONE repo, so am not sure how to include this into metacat-index</p> Feature #7173 (New): Add the measurementScale to the EML .xsl stylesheetshttps://projects.ecoinformatics.org/ecoinfo/issues/71732017-01-25T22:07:33ZLauren Walkerwalker@nceas.ucsb.eduFeature #7099 (New): Create a new admin page for Metacat admins to register schemashttps://projects.ecoinformatics.org/ecoinfo/issues/70992016-08-30T21:27:53ZJing Taotao@nceas.ucsb.edu
<p>Currently we add new schemas base on Metacat release sand occasionally add it by sql commands. <br />We will disable Metacat to download external schemas and reject a xml object if the schema of the object can't be found locally.(<a class="external" href="https://projects.ecoinformatics.org/ecoinfo/issues/7096">https://projects.ecoinformatics.org/ecoinfo/issues/7096</a>). So we believe the request of adding new schemas will increase. We need provide a admin page to register schemas.</p> Feature #6951 (New): Develop XSLT for ISO-19119 for Member Node Serviceshttps://projects.ecoinformatics.org/ecoinfo/issues/69512016-01-20T22:46:13ZLauren Walkerwalker@nceas.ucsb.edu
<p>There are details in the ISO-19119 XSLT that may be useful to expose to users through the D1 view service / MetacatUI Metadata View.</p> Feature #6848 (New): Add link to send another verification emailhttps://projects.ecoinformatics.org/ecoinfo/issues/68482015-09-30T16:29:26ZLauren Walkerwalker@nceas.ucsb.edu
<p>This has been something suggested by a few users when they don't get their original verification email</p> Feature #6554 (New): Tag the Metacat doc pages to populate the docs indexhttps://projects.ecoinformatics.org/ecoinfo/issues/65542014-05-13T20:36:24ZLauren Walkerwalker@nceas.ucsb.edu
<p>The Metacat docs index is pretty sparse right now with only 2 terms. It would be pretty simple to go through each page of the docs and add index tags so that Metacat developers can find information in the docs quickly.</p> Feature #6445 (New): Alter replicaPolicies.sh so that the script will iterate over pages of objec...https://projects.ecoinformatics.org/ecoinfo/issues/64452014-03-05T19:34:46ZLauren Walkerwalker@nceas.ucsb.eduFeature #6416 (In Progress): Do not allow restrictive access control change to content with a DOIhttps://projects.ecoinformatics.org/ecoinfo/issues/64162014-02-11T18:34:16Zben leinfelderleinfelder@nceas.ucsb.eduFeature #6362 (New): Add an id to the year element in the citation in eml-indentifier.xslhttps://projects.ecoinformatics.org/ecoinfo/issues/63622014-01-06T19:30:51ZLauren Walkerwalker@nceas.ucsb.eduFeature #6355 (New): Print "N/A" or similar when EML fields don't exist rather than print a blank...https://projects.ecoinformatics.org/ecoinfo/issues/63552014-01-03T22:35:02ZLauren Walkerwalker@nceas.ucsb.eduFeature #6034 (New): Simplify configuration for certificate delegationhttps://projects.ecoinformatics.org/ecoinfo/issues/60342013-07-09T21:32:35Zben leinfelderleinfelder@nceas.ucsb.edu
<p>So we don't loose this in the shuffle - we could probably fill out some of the MyProxy configuration values based on Metacat properties. But I don't think we can really generate provate keys and register nodes with CILogon...</p> Feature #5989 (In Progress): Track data download, view and citation statisticshttps://projects.ecoinformatics.org/ecoinfo/issues/59892013-05-25T01:14:28ZMatt Jonesjones@nceas.ucsb.edu
<p>Currently the only usage stats we have in Metacat are the raw logs. This new service would provide several statistical reports in machine-readable format intended for efficient use on clients for building user interface displays that show those statistics.</p>
<p>The service should include the following response statistics, and be extensible to add other tracked statistics as needed:</p>
<ol>
<li>Number of views (defined as number of times the metadata has been viewed on the web)</li>
<li>Number of package downloads (needs definition)</li>
<li>Size in bytes of package downloads</li>
<li>Number of citations (implement in a second phase)</li>
</ol>
<p>For each of these statistics, calling apps should be able to constrain the results to only include records matching:</p>
<ol>
<li>a PID or list of PIDs</li>
<li>creator or list of creators (DN, or ORCID, or some amalgam -- to be discussed)</li>
<li>a time range of access event (upload, download, etc.)</li>
<li>? spatial location of access event (upload, download, etc.)</li>
<li>? IP Address</li>
<li>accessor or list of accessors (DN, or ORCID, or some amalgam, needs ACL -- to be discussed)</li>
</ol>
<p>For each of these statistics, calling apps should be able to request the statistic aggregated by several specific facets, including the following (in order of importance):</p>
<ol>
<li>User (DN, or ORCID, or some amalgam -- to be discussed)</li>
<li>Time range, aggregated to requested unit (day, week, month, year)</li>
<li>? Spatial range, aggregated to requested unit (to be discussed)</li>
</ol>
<p>Intersections of these aggregated facets should also be possible, but are a lower priority than the facets alone. For example, when finished, one should be able to request the following reports, among others:</p>
<ol>
<li>{Views,Downloads,Bytes,Citations} for a given pid or list of pids</li>
<li>{Views,Downloads,Bytes,Citations} by user (aggregates across pids)</li>
<li>{Views,Downloads,Bytes,Citations} by month (aggregates across pids)</li>
<li>{Views,Downloads,Bytes,Citations} by spatial location (aggregates across pids)</li>
<li>{Views,Downloads,Bytes,Citations} for a given pid by month for a specific time range</li>
<li>{Views,Downloads,Bytes,Citations} by user by month</li>
<li>etc.</li>
</ol>
<p>The download format (JSON?, XML?) should allow for an extended set of response variables, and an extendable set of aggregating facets. Need to discuss, but probably XML as that is DataONE's initial choice for all other services. Contemplate both if useful.</p>
<p>The REST API for this service should be developed in the DataONE space, with intention of it being implementable by both other MNs and CNs in DataONE.</p>