Allow choice of metacat server at install
On initial profile creation or installation the user should be able to choose the metacat to point
to. A default behavior could be: if o=lter then metacat=knb.lternet.edu. The user would then be
presented with a confirmation screen. If everything is ok, then proceed else here are other
choices. User could then be given a list of other metacats including option to add local metacat.
#1 Updated by Matt Jones over 20 years ago
I've been thinking of something similar but not quite the same. I think the
user should be able to configure a list of metacat servers that can be used in
priority order, rather than just one. This will then act as a failover option.
If the first metacat server does not respond, we try the next in the list, etc.
till we run out of servers. For sites like NCEAS/LTER where we'll be
replicating each other's content, that will make it a nice failsafe system.
Then the question becomes, which metacat servers do we want to ship as default.
David's suggestion that the server URL be moved to the profile (rather than
config.xml) and that we ask the user upon creation of the profile has merit.