Skip to content

Releases: diging/conceptpower

Release v3.5

04 Dec 22:31
09aeeb6
Compare
Choose a tag to compare

Release notes - ConceptPower - Version v3.5

Bug

  • [CCP-234] - When a search term include a hyphen, it is not found
  • [CCP-235] - Search term needs to be trimmed before searching
  • [CCP-236] - REST interface search doesn't seem to include all merged ids
  • [CCP-238] - If wordnet description contains quotation marks, wrappers can't be created from search page
  • [CCP-243] - When searching, if there are additional blanks around a search term, terms are not found

New Feature

  • [CCP-230] - Search needs to search normalized values

Release v3.4

17 Jul 21:38
Compare
Choose a tag to compare

Release Notes - Conceptpower - Version v3.4

Bug

  • [CCP-233] - Search is case sensitive, but rest interface search makes everything lowercase

New Feature

  • [CCP-206] - Details view of a concept needs to show merged ids
  • [CCP-212] - Search in GUI interface needs to do pagination in backend
  • [CCP-213] - Concept lists page needs to say for which concept list it shows the concepts
  • [CCP-225] - When logged in there should be a button in the concept tables to create wordnet wrappers
  • [CCP-229] - When I finish creating a concept, I'd like to be redirected to see the details of that new concept

Release v3.3

24 Apr 22:31
Compare
Choose a tag to compare

Bug

  • [CCP-209] - Odd search results: searching for "be" as noun returns "united states intelligence agency" as first result
  • [CCP-210] - In REST Concept Search: when I use a field name that doesn't exist, CP return a 500
  • [CCP-217] - Merged ids in RESTful api call
  • [CCP-218] - Query with merged wordnet id
  • [CCP-221] - Creating wordnet wrappers: selecting one doesn't really work
  • [CCP-222] - Merging concepts doesn't seem to update the index properly
  • [CCP-224] - ConceptLookup returns results that are very oddly sorted
  • [CCP-227] - Editing concept: adding a wordnet id, doesn't seem to update the index
  • [CCP-228] - Creating concept wrappers: when there is a validation error, the whole form is reset

New Feature

  • [CCP-211] - REST Search: search in equal_to field for a value that does exist in CP, return no results

Release v3.2

27 Mar 18:44
Compare
Choose a tag to compare

Bug

  • [CCP-111] - Forgot Password Email Not Sent.
  • [CCP-142] - On the index page, there is a black box at the top of the page.
  • [CCP-144] - On some pages, the drop down menus have extra bullets
  • [CCP-145] - When I try to add a synonym to a concept, I get a greyed out screen.
  • [CCP-146] - Some pages are missing the favicon
  • [CCP-149] - Method getTotalNumberOfWordsIndexed needs a little work and another name.
  • [CCP-150] - User table needs some adjustments
  • [CCP-156] - Concept lists: descriptions of concepts are not shown.
  • [CCP-162] - When words are indexed for first time, last run timestamp is not updated
  • [CCP-164] - Select Wordnet concept from search results
  • [CCP-167] - Create new concept shows datatable alert if one search for empty string in VIAF
  • [CCP-168] - Adding new concept: hitting enter in search VIAF input should not submit form
  • [CCP-169] - When searching VIAF, sometimes it shows just question marks.
  • [CCP-170] - Description field in tables need to render html (right now it shows <i> and <br>)
  • [CCP-173] - Search results only show a maximum of 10 results, no matter what
  • [CCP-188] - ConceptSearch by "equals_to" does not return results
  • [CCP-189] - There are (at least) three different predicates for "equals" across the application
  • [CCP-192] - No search results throws error
  • [CCP-193] - REST serach api returns wrong results
  • [CCP-196] - When calling the API while the indexer is running it doesn't show a correct error message.
  • [CCP-208] - Concept search page always shows just one page
  • [CCP-214] - REST api search: value of pos isn't case-insensitive
  • [CCP-215] - REST api search: default operator for search should be 'and'

New Feature

  • [CCP-82] - Provide scroller for description of concepts in concept search , wordnet wrapper add and converting normal concept to wrapper pages .
  • [CCP-135] - Return RDF format from API
  • [CCP-136] - Change history recording
  • [CCP-138] - Add new Concept should use a backing bean.
  • [CCP-141] - There should be an API method that lets other applications create ConceptWrappers.
  • [CCP-157] - REST add method needs to add URI of added concept to returned JSON
  • [CCP-163] - In rest interface, all possible ids need to be returned for a concept.
  • [CCP-171] - We need the functionality back to make a concept a concept wrapper.
  • [CCP-172] - We need paginating functionalities for concepts in concept lists
  • [CCP-174] - Timeout for conceptpower session needs to be longer
  • [CCP-175] - REST API search: user should be able to specify how many results per page they want to get back
  • [CCP-176] - REST Api search: add pagination
  • [CCP-177] - Search on GUI: pagination should be done on backend side
  • [CCP-181] - REST search should return json when requested
  • [CCP-185] - Return concept alternative ids
  • [CCP-186] - We need a merge functionality for concepts
  • [CCP-194] - REST search needs to allow search without POS
  • [CCP-202] - We need integration tests for all REST methods

Test Chore

  • [CCP-203] - Unit Test for Rest API

Chore

  • [CCP-187] - Can deleted concepts still be found when called by there id?

Release Version v3.1

17 Aug 18:07
Compare
Choose a tag to compare

Bug

  • [CCP-159] - Modifying a concept adds a second entry to lucene

New Feature

  • [CCP-160] - Add profile page where user can change their password.
  • [CCP-161] - Add forgotten password functionality missing in new layout

Release Version v3.0

14 Jul 19:37
Compare
Choose a tag to compare

Release Notes - ConceptPower - Version v3.0

Bug

  • [CCP-143] - There is a lot of text with the wrong font on the pages.
  • [CCP-147] - When I try to edit a concept I get an exception.
  • [CCP-148] - Indexer running message needs to be changed.
  • [CCP-151] - 3-party libraries have to be part of the war file unless they can be accessed through https
  • [CCP-152] - The REST method to add concepts is not the latest that is in master
  • [CCP-153] - domain classes have to stay in their orignial package, or we can't read already created object anymore
  • [CCP-155] - There are a bunch of commits in master (hotfixes for the current version) that aren't in develop.

New Feature

  • [CCP-128] - Implement Lucene for searching
  • [CCP-133] - New layout for Conceptpower
  • [CCP-140] - When login fails, a message should be shown to the user.
  • [CCP-154] - When submitting a new concept through REST, type needs to be validated

Test Chore

  • [CCP-132] - Writing test cases for left out classes

Release Version v2.0.5

13 Jul 01:18
Compare
Choose a tag to compare
  • Solves encoding issue with non-ascii characters.

Release Version v2.0.4

29 Apr 20:42
Compare
Choose a tag to compare
  • Proper error code is sent when user sends wrong JSON to add concepts API method.
  • Description of concepts is correctly shown on search page.

Release Version v2.0.3

27 Apr 23:30
Compare
Choose a tag to compare
  • When adding a concept through API, type is validated.
  • 'types' attribute in json payload replaced with 'type'

Conceptpower v2.0.2

31 Mar 16:57
Compare
Choose a tag to compare

Bug

  • [CCP-139] - API returns control characters in XML