[ 
https://jira.duraspace.org/browse/DS-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27649#comment-27649
 ] 

Ivan Masár commented on DS-1456:
--------------------------------

Yes, the meta tag is what I was originally thinking of. The downside is that it 
can be (too) easily changed by the user.


Service description standards

SWORD has Atom's Service Document:
http://bitworking.org/projects/atom/rfc5023.html#appdocs

OAI-PMH has it's own format:
http://www.openarchives.org/OAI/openarchivesprotocol.html#Identify

then there's WSDL by W3C:
http://en.wikipedia.org/wiki/Web_Services_Description_Language
which has a Java implementation in Apache Axis and what do you know, we already 
include Axis as a dependency (though we probably need an additional jar for 
WSDL).


About privileged contexts - I suspected that it's something like that. I agree 
that it wouldn't be worth it.


The bad thing about just using dspace.url is that DSpace is often deployed on 
the domain root, so you can't tell it from that. But we can fetch the HTML and 
spit out the value in the meta tag (after including the interface ID in there).
                
> "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

Reply via email to