https://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2017-03-15T18:02:06ZDataONE TasksMember Nodes - Task #8047: Investigate how to maintain identity/"branding" of a sub-repository's content on a DataONE MNhttps://redmine.dataone.org/issues/8047?journal_id=286202017-03-15T18:02:06ZLaura Moyerslmoyers1@utk.edu
<ul><li><strong>Related to</strong> <i><a class="issue tracker-9 status-9 priority-4 priority-default parent" href="/issues/8035">MNDeployment #8035</a>: IEDA_EarthChem Library (Interdisciplinary Earth Data Alliance)</i> added</li></ul> Member Nodes - Task #8047: Investigate how to maintain identity/"branding" of a sub-repository's content on a DataONE MNhttps://redmine.dataone.org/issues/8047?journal_id=288382017-05-03T19:42:09ZLaura Moyerslmoyers1@utk.edu
<ul></ul><p>We had talked internally about the question of "branding" in DataONE. Currently DataONE communicates only the MN "brand" in search results, etc. We could accommodate a source/originating repository in science metadata. </p>
<p>Discussion at a meeting with IEDA 5/3/17 took this further, to include in the science metadata of an object the original source (repository) of the data, either by text, website, or logo, and modify the search UI to display that value as a sub-brand of the MN.</p>
<p>IEDA is using ISO 19115 metadata. There are other MNs who serve content from multiple sources who might be interested in this functionality if it were available (LTER? EDI?).</p>
Member Nodes - Task #8047: Investigate how to maintain identity/"branding" of a sub-repository's content on a DataONE MNhttps://redmine.dataone.org/issues/8047?journal_id=289112017-06-25T13:07:14ZLaura Moyerslmoyers1@utk.edu
<ul></ul><p>Current status: awaiting free cycles for Lauren and Dave to evaluate how metadata (ISO 19115 in this case) could be used to identify and display sub-branding. We hope to identify and mock-up a solution to share with IEDA. </p>
Member Nodes - Task #8047: Investigate how to maintain identity/"branding" of a sub-repository's content on a DataONE MNhttps://redmine.dataone.org/issues/8047?journal_id=299112018-02-19T16:20:44ZMonica Ihliemail@monicaihli.com
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>Closing this ticket as the investigative process has been completed. The solution that will be developed will be the ability to host multiple nodes from a single installation of the GMN web app. Since branding is tied to node identity, this approach confines code changes to the MN software only without touching other parts of the overall system. See ticket <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Story: Develop Ability to Host Multiple Nodes from a Single Installation of GMN Web App (Closed)" href="https://redmine.dataone.org/issues/8371">#8371</a> for details.</p>