Questions re: implementation at Darien
Questions about the SOPAC module based on the implementation at Darien:
1. Under the "Fine-tune by location" option, it appears that you are showing location codes from Millennium, which might not mean anything to customers (I know our customers would have a hard time deciphering our location codes). Are there other options for displaying that information? Could we display only the branch, or the location label instead of the code?
2. Are the "sort-by" options customizable? Could we, for example, add a "sort by title" or "sort by publication date" in addition to the options you have listed?
Genesis,
1) Those location codes are displayed that way because we've been changing location codes like crazy in Darien and I haven't yet reflected those changes in Locum, so they're not resolving to anything. My bad.
2) Yes, you can sort by a number of criteria. Adding those options in is a templating issue at this point.
A couple more questions about Darien's implementation:
1.) The production requirement for memory is 10 GB. Is Darien currently using 10 GB or more?
2.) Due to a server limitation of 8 GB, (and I know there are a few variables that come into play here, but off the top of your head...) could 8 GB do the job?
Thanks!
Erik
Erik, 8GB should be more than enough. The production requirement is actually not 10GB, but it is what we are running on our production server. Our development box, however, has 1GB of memory--it's an old clunker, yet it still runs quite well. I wouldn't suggest that for production, of course, and your milage is going to vary depending on how many records you're planning on harvesting. Since Locum loads a heap table into memory so that it can quickly piece together the facet data, you're going to want to at least match the requirements of that table, and probably double it (totally unscientific rule of thumb).