MetacatUI: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362016-11-03T21:39:20ZEcoinformatics Redmine
Redmine Task #7152 (Resolved): Identifier filter should search the 'documents' and 'resourcemap' fields toohttps://projects.ecoinformatics.org/ecoinfo/issues/71522016-11-03T21:39:20ZLauren Walkerwalker@nceas.ucsb.edu
<p>Currently it just searches the id field which only matches against metadata</p> Task #7151 (Resolved): Take out "Only results with data" filter from the Arctic Data Center theme...https://projects.ecoinformatics.org/ecoinfo/issues/71512016-11-03T21:38:05ZLauren Walkerwalker@nceas.ucsb.edu
<p>See this ticket for the underlying issue: <a class="external" href="https://projects.ecoinformatics.org/ecoinfo/issues/7150">https://projects.ecoinformatics.org/ecoinfo/issues/7150</a></p> Task #7056 (Closed): Investigate schema-based JS object generationhttps://projects.ecoinformatics.org/ecoinfo/issues/70562016-07-15T17:30:02ZChris Jonescjones@nceas.ucsb.edu
<p>We've acknoledged that it is difficult to manually represent the entire EML schema as Javascript Backbone models, much less other metadata schemas. Investigate converting EML instance documents into Javascript objects and vice versa. Test some of the schema binding libraries that do this.</p> Task #7050 (Resolved): Develop the 'Add a Nested Dataset' use casehttps://projects.ecoinformatics.org/ecoinfo/issues/70502016-07-06T21:57:29ZChris Jonescjones@nceas.ucsb.edu
<p>This use case describes adding a dataset folder into an existing dataset folder. This will likely be targeted for the 2.1.0 release. See <a class="external" href="https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/use-cases/add-a-nested-dataset.rst">https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/use-cases/add-a-nested-dataset.rst</a></p> Task #7049 (Resolved): Develop the 'View Public Metadata' use casehttps://projects.ecoinformatics.org/ecoinfo/issues/70492016-07-06T21:55:15ZChris Jonescjones@nceas.ucsb.edu
<p>This use case describes public viewing of a metadata record using the mocked up layout. This differs slightly from the editor view (when logged in as a user with editing rights). See <a class="external" href="https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/use-cases/view-public-metadata.rst">https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/use-cases/view-public-metadata.rst</a></p> Task #7048 (Resolved): Develop the 'Update Metadata' use casehttps://projects.ecoinformatics.org/ecoinfo/issues/70482016-07-06T21:52:56ZChris Jonescjones@nceas.ucsb.edu
<p>This use case describes providing metadata details for a selected dataset folder. The editing would apply to the Summary section, or any other section that demonstrates the functionality. See <a class="external" href="https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/use-cases/update-metadata.rst">https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/use-cases/update-metadata.rst</a></p> Task #7047 (Closed): Develop the 'Add Metadata' use casehttps://projects.ecoinformatics.org/ecoinfo/issues/70472016-07-06T21:50:04ZChris Jonescjones@nceas.ucsb.edu
<p>This use case describes adding a dataset folder that will contain data files. The dataset folder represents the science metadata description of the data.</p> Task #7046 (Closed): Develop the 'Remove a file' use casehttps://projects.ecoinformatics.org/ecoinfo/issues/70462016-07-06T21:48:25ZChris Jonescjones@nceas.ucsb.edu
<p>This use case describes removing a file, or set of files.</p> Task #7045 (Closed): Develop the 'Rename a file' use casehttps://projects.ecoinformatics.org/ecoinfo/issues/70452016-07-06T21:47:15ZChris Jonescjones@nceas.ucsb.edu
<p>This use case describes renaming a data file.</p> Task #7044 (Closed): Develop the 'Upload Data' use casehttps://projects.ecoinformatics.org/ecoinfo/issues/70442016-07-06T21:46:06ZChris Jonescjones@nceas.ucsb.edu
<p>This use case describes choosing and uploading files to the repository.</p> Task #7043 (Resolved): Develop use case documents for basic editor functionshttps://projects.ecoinformatics.org/ecoinfo/issues/70432016-07-06T21:44:41ZChris Jonescjones@nceas.ucsb.edu
<p>We need to write up each of the main use cases for managing data and metadata in the new editor. We've started on this here:</p>
<p><a class="external" href="https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/editor-design.rst">https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/editor-design.rst</a></p>
<p>The table in the above document lists the current use cases.</p> Task #7042 (Resolved): Develop mockup images for editor use caseshttps://projects.ecoinformatics.org/ecoinfo/issues/70422016-07-06T21:41:18ZChris Jonescjones@nceas.ucsb.edu
<p>We need to create mockups for each editor use case showing the general functionality, layout, etc. We've started on these in the NCEAS Design git repo in the MetacatUI/Editor-Refactor folder:</p>
<p><a class="external" href="https://code.nceas.ucsb.edu/git/nceas-staff/nceas-design/MetacatUI/Editor-Refactor/">https://code.nceas.ucsb.edu/git/nceas-staff/nceas-design/MetacatUI/Editor-Refactor/</a></p> Task #7041 (Resolved): Develop a design document to steer software development.https://projects.ecoinformatics.org/ecoinfo/issues/70412016-07-06T21:35:22ZChris Jonescjones@nceas.ucsb.edu
<p>We need to write an overarching design document that will guide the implementation of the editor. We've started this effort here: <a class="external" href="https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/editor-design.rst">https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor/editor-design.rst</a></p> Task #6992 (Resolved): Replace 'authenticatoin_token' text depending on deployment environmenthttps://projects.ecoinformatics.org/ecoinfo/issues/69922016-03-22T21:08:23ZPeter Slaughterslaughter@nceas.ucsb.edu
<p>Currently the user profile "Token for DataONE R" tab generates text for the R option named "authentication_token". The R client has been updated so that a different option name needs to be printed depending on whether the token is being created for the<br />production environment (i.e. from search.dataone.org) or for a test environment (search*.test.dataone.org). For production, the option name should be "dataone_token" and for test environments it should be "dataone_test_token". (This is <br />fully described at <a class="external" href="https://github.com/DataONEorg/rdataone/issues/139">https://github.com/DataONEorg/rdataone/issues/139</a>)</p> Task #6946 (Resolved): Create mockup of the services display in metadata and search result viewshttps://projects.ecoinformatics.org/ecoinfo/issues/69462016-01-20T17:38:24ZLauren Walkerwalker@nceas.ucsb.edu
<p>The services will be displayed in three locations:</p>
<p>- The Metadata View for data sets with objects loosely coupled to a service<br />- The Metadata View for the service itself<br />- The SearchResult views for loosely coupled services - probably the only difference will be an icon indicating that search result is a service</p>