[
https://jira.duraspace.org/browse/DS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27650#comment-27650
]
Mark H. Wood commented on DS-1456:
----------------------------------
About dspace.url: I should have written more. I was suggesting that we simply
provide the URL so that someone can manually go and look at it, with assurance
that that is the instance at issue. "What's the simplest thing that could
work?"
PMH is actually an example of what is lacking. If I come to
http://dspace.example.com/ and find a DSpace home page there, how would I know
the URL for the associated PMH responder (if there is one)? You can find out a
lot about a PMH responder with verb=Identify but you have to know where it is
first. How can things like DSpace tell you where their ancillary services are?
Having found http://dspace.example.com/, how can I get it to tell me where is
PMH, where is SWORD, where is ORE.... Maybe WSDL can do that -- gotta make
time to read that book I bought. (Looking back, I see that I asked the wrong
question: not self-describing services, but self-describing websites which
could be constellations of distinct services.)
We shouldn't spend a lot of worry on the site owner changing tags. He's got
the source and can change anything he pleases. But if he changes certain
things, we can't help anymore. So he has an incentive not to change those
things. There's nothing wrong with being forced to say, "well, you broke the
diagnostic tool, so you'll have to do some more digging for the information we
need to help you. Here's how."
> "dspace version" command-line script
> ------------------------------------
>
> Key: DS-1456
> URL: https://jira.duraspace.org/browse/DS-1456
> Project: DSpace
> Issue Type: New Feature
> Reporter: Ivan Masár
> Assignee: Mark H. Wood
>
> We should provide a "[dspace]/bin/dspace version" script, which would gather
> the basic information about DSpace and its environment that is necessary to
> ask questions on dspace-tech.
> This information includes most prominently:
> * DSpace version
> * OS version
> * UI(s) used
> * is Discovery enabled?
> somewhat less often important:
> * JDK version
> * ant version
> * maven version
> * path to DSpace
> Optional flags could produce even more information, pulled from
> configuration, e.g. database configuration, hostname/URL configuration,
> authentication configuration (with passwords omited), etc.
> Most of this information is already available in the XMLUI admin Control
> panel, so some of those methods could be reused.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
