Query Generator: context query: link with specific community or claimed in community's dashboard
Updates to Migrate community claims from Beta to Production
CommunityUtils: chnage methods from static, add it with autowired in EmailSender update properties
Fix1: set type after parsing response from external sources - this fix puts the record in the proper file path
Fix2: Update orcid parser, use single orcid work response update ExternalParserTest
ClaimEntity: Add information about the dashboard where the claim was created
Properties: add properties for the different services create beans properly production or beta is decided from the services urls in properties
Migration: create migration method: CopyFromBetaToProduction for communities
Search utils, Project Handler, IndexResultHandler: get search service url from properties remove isProduction parameter remove dedup result methods used in migration
-> update method calls and signatures accordingly
- rename properties files springContext-claimsDemo.xml --> springContext-claims.xml- rename properties paths services.claimsDemo.* to services.claims.*
-Remove methods and classes used for the migration from old database schema to new-Remove communities XMLs-rearrange packages (remove 'migration' and 'claimsDemo') Properties paths didn't change!
Parsing Orcid records: fix parsing issue, add one more test
1. pom.xml: Add commented plugin for surfire (possibly needed in openjdk: bug in their release) | update version of javax.mail.2. FetchContextHandler.java: bug fix in parsing resultset.3. QueryGenerator.java: bug fix in query of method 'generateSelectFirstContextByCommunityIdQuery'....
NotificationHandler.java & EmailSender.java: bug fix in calculating seconds (store 12:00 and add 1 sec to last_interaction_date when sending email).
1. FetchClaimHandler.java: add method fetchNumberOfClaimsByDateAndOpenaireId.2. CommunityUtils.java: request datasource API to get community information (including managers).3. FetchContextHandler.java: Method fetchFirstContextByCommunityId to parse name of community to be used in the above API....
1. Add entity 'Notification': pairs of mail-openaireId, with the preferences for notifications of this user for this id.2. Add FetchNotificationHandler and NotificationHandler for 'Notification' entity.3. springContext-claimsDemo.xml: Add beans for FetchNotificationHandler, NotificationHandler, defaultFrequencyInHours....
1. Project.java: Remove 'token' field from 'Project' entity.2. FetchProjectHandler.java, ProjectHandler.java, TestClass.java: Remove methods related to 'token' field.3. FetchProjectHandler.java: Add 'fetchProjectIdsAndNamesByProjectManagerMail' method | Change 'fetchContactEmailsByProjectId' method (mails are returned as List from DAO).
Parameterize context utils methods with a boolean parameter for productionIndex, add production urlIn delete claims method add check for deleting record
Enable claiming for ORPsSet direct index url in propertiesMigration: save orphan Ids, claims uncomment fetch dedup
1. FetchProjectHandler.java: Rename 'fetchProjectIdByToken' to 'fetchProjectIdByTokenAndEmail' and create 'public String fetchProjectIdByToken(String token)' method.2. QueryGenerator.java: Rename 'generateSelectProjectIdByTokenQuery' to 'generateSelectProjectIdByTokenAndEmailQuery' -...
Change ContextUtils to get concept label from new Context API
add communities xml files| change fetching methods for communities | set properly date in migration | change ORCID API
change migration procedure: search first in beta then in production| add software | change directIndexHandler check for response
Delete file when claim is deleted and result has no other links| change semantics | change the openaireId generation
prepared statements for the sql queries
claims-demo folder renamed to trunk
Copy for Java8