David Ghedini

After using NGASI App Manager for several years, we were pretty unhappy to learn they were going out of business.

We took the opportunity to develop our own Java provisioning system, CoffeeCP.

CoffeeCP is available for cPanel, as well as Virtualmin and Webmin (with other control panels soon to come).

It can be provisioned via WHMCS or directly on your servers.

Unlike NGASI, CoffeeCP is not a Java application itself, so it has a very small footprint.

Also unlike NGASI, it is not a separate control panel, users access all functions via cPanel, Webmin, etc..

The cPanel version is built with JSON and PHP and the Virtualmin and Webmin versions are built with Perl.

So, no extra overhead.

If you are or were a NGASI user, or just want to add Java to your hosting offerings, have a look at CoffeeCP

All plans include Unlimited Installations, so you also have the benefit of a fixed monthly overhead and won’t need to buy additional licenses for each VM or server you turn up.

To display the number of submissions for each Community, change value of “webui.strengths.show” from “false” to “true” in dspace.cfg as show below:

# Whether to display collection and community strengths (i.e. item counts)
# XMLUI only makes strengths available to themes if this is set to true!
# To show strengths in the XMLUI, you also need to create or use a theme which
# displays them.
webui.strengths.show = true

# if showing strengths, should they be counted in real time or
# fetched from cache?
#
# Counts fetched in real time will perform an actual count of the
# index contents every time a page with this feature is requested,
# which may not scale as well as a cached count.
# The default behaviour is to use a cache.
# webui.strengths.cache = true

# Whether to display collection and community strengths (i.e. item counts)

# XMLUI only makes strengths available to themes if this is set to true!

# To show strengths in the XMLUI, you also need to create or use a theme which

# displays them.

webui.strengths.show = true

# if showing strengths, should they be counted in real time or

# fetched from cache?

# Counts fetched in real time will perform an actual count of the

# index contents every time a page with this feature is requested,

# which may not scale as well as a cached count.

# The default behaviour is to use a cache.

# webui.strengths.cache = true

Note: By default, an index count will be performed in real time when pages are loaded. If you wish to prevent this, uncomment “webui.strengths.cache = true” and set the value to “false”

An alternative to NGASI

DSpace: Display Number of Items in Community