[
http://jira.dspace.org/jira/browse/DS-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10882#action_10882
]
Robin Taylor commented on DS-405:
---------------------------------
Just a thought - Should the configuration for the @Mire stats module be in
dspace.cfg ? I thought the plan was to try and slim down dspace.cfg to only
contain the config for core DSpace ? I think it would be preferable to have
optional modules like the stats module have their configuration in their own
config files.
> New 1.6 Statistics settings in dspace.cfg need Documentation
> ------------------------------------------------------------
>
> Key: DS-405
> URL: http://jira.dspace.org/jira/browse/DS-405
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 1.6.0
> Environment: Any
> Reporter: Tim Donohue
> Assignee: Jeffrey Trimble
>
> The settings for the new 1.6 Statistics feature need better documentation
> overall.
> (1) In the installation/upgrade instructions, we should be telling folks that
> they need to have the "solr" web application installed for Statistics to
> work. This doesn't seem to be stated anywhere.
> (2) There's confusion over which fields in dspace.cfg correspond to the new
> Statistics feature. Obviously, the following fields seem to correspond to
> the new 1.6 Stats. Unfortunately, they are NOT documented anywhere.
> solr.log.server = ${dspace.baseUrl}/solr/statistics
> solr.spidersfile = ${dspace.dir}/config/spiders.txt
> solr.dbfile = ${dspace.dir}/config/GeoLiteCity.dat
> useProxies = true
> statistics.items.dc.1=dc.identifier
> statistics.items.dc.2=dc.date.accessioned
> statistics.items.type.1=dcinput
> statistics.items.type.2=date
> statistics.default.start.datepick = 01/01/1977
> statistics.item.authorization.admin=true
> (3) Are the following Dspace.cfg fields still used by the new 1.6 Statistics?
> If not, we need to either document this well or remove them altogether:
> ###### Statistical Report Configuration Settings ######
> # should the stats be publicly available? should be set to false if you only
> # want administrators to access the stats, or you do not intend to generate
> # any
> report.public = false
> # directory where live reports are stored
> report.dir = ${dspace.dir}/reports/
> (4) How does one choose to make the new 1.6 Statistics publicly available
> (they seem to default to being restricted)? Claudia and I (Tim) are trying
> to figure this out for the testathon, and it seems undocumented -- so we're
> having to try and dig around through code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
