Project

General

Profile

Task #844

Story #956: Fix problems with Metacat 0.5 implementation

Remove dryad sql & schema statements from metacat proper

Added by Robert Waltz almost 12 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
High
Assignee:
Chad Berkley
Category:
Metacat
Target version:
Start date:
2010-10-06
Due date:
% Done:

0%

Milestone:
CCI-0.6
Product Version:
*
Story Points:
Sprint:

Description

We should maintain a separate script for updating metacat after all other database updates have taken place post-configuration. Instead of maintaining a bogus dryad schema in metacat itself, we should either point the DB entries to an URL or copy in schemas to correct directory post configuration.

History

#1 Updated by Chad Berkley over 11 years ago

  • Tracker changed from Task to Bug
  • Start date set to 2010-10-06

#2 Updated by Matthew Jones over 11 years ago

  • Milestone set to CCI-0.6
  • Target version deleted (CCI-0.6)
  • Parent task set to #956

#3 Updated by Chad Berkley over 11 years ago

  • Status changed from New to In Progress

Robert, I don't see any dryad scripts in metacat. Where are they being added? Is this a post-install CN step that is added? The only dataone related schema that Metacat loads by default is this one:

INSERT INTO xml_catalog (entry_type, public_id, system_id)
VALUES ('Schema', 'http://dataone.org/service/types/common/0.1', '/schema/D1_SCHEMA_0_4/common.xsd');

See metacat/src/loaddtdschema-postgres.sql.

#4 Updated by Chad Berkley over 11 years ago

  • Status changed from In Progress to Rejected
  • translation missing: en.field_remaining_hours set to 0.0

Has already been done.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)