1. BibSonomy Avatar BibSonomy
  2. General
  3. BibSonomy

Wiki

Clone wiki

BibSonomy / documentation / releases / 2015 / 3.1.0

View History

3.1.0 (PUMA2 final jil+sdo)

Date: 2015/02/25

Issues: https://bitbucket.org/bibsonomy/bibsonomy/issues?milestone=3.0.0&milestone=3.0.1&milestone=3.1&milestone=3.1.1&status=open&status=new

released

external

  • shared Index with PUMA
  • inspected community posts
  • community posts
    • approved versions
  • post history
  • group restructuring
  • federated search (using elasticSearch)
  • updated Lucene
  • Pingback

internal

  • scraper fixes ?
  • now using lucene-4.8.1
  • new date in sync

Necessary Changes

  • new lucene indices must be built. This could be done in advance on a slave (see Generating Luceneindex from Database manually) . bibsonomy.properties can be edited to use a new lucene index folder with the index from the slave before deploying the new release.

properties

  • The following property controls wether users are checked by the spam-framework (1) or always accepted as non-spammers (0)

    • user.defaultToClassify=1 (bibsonomy) (default 1)
    • user.defaultToClassify=0 (PUMA)

  • elasticsearch (kann man auch erstmal leer lassen um das Feature deaktiviert zu lassen) (default leer)

    • es.address = localhost:9300
    • es.cluster.name = bibsonomy-world
  • new group property for automatic or supervised creation of groups
    • project.groupcreationmode = requestedbased (gandalf, default)
    • project.groupcreationmode = automatic (puma)

batch scripts

groups

  • update delete_pending_users.pl (on daffy?)

other software

database

inspected posts, groups, history

#!sql
-- before Release --
add_inspected_posts.sql
goldstandard_repair_new_content_id.sql
restore_current_content_id.sh
create_indexes_for_history.sql
new_bookmark_index.sql

-- when BibSonomy is down --
change_group_column_names.sql
group.sql
update_groups.sql

-- when BibSonomy is back up --
-- yes we execute the script twice in case someone updated a post after the script above finished and before the release
restore_current_content_id.sh

Tomcat Config

  • updated bibsonomy-util to 2.4.0
  • reconfigured log4j.xml to filter from errorLogs and to write to knownExceptions log: Request processing failed; nested exception is org.springframework.web.multipart.MultipartException: Could not parse multipart servlet request; nested exception is org.apache.commons.fileupload.FileUploadException: Stream ended unexpectedly

Updated