dnet45dhp-schemasdnet-hadoopdnet40dnet50
[Trunk | Claims Service]:1. ManagerUtils.java: Added method "isCommunityManager()" to check if a user_email is among managers of a community.2. springContext-claims.xml: Added in bean with id=emailSender, property name="managerUtils" and removed property name="communityUtils".
[Trunk | Claims Service]:1. ManagerUtils.java: [NEW] File for getting community managers from registry service added.2. springContext-claims.properties: Property "services.claims.registryAPIForManagerEmails" added - URL of registry service for requesting community manager emails....
- fix order by titles- context query: get results made in the same dashboard- add claimed_in_dashboard in the result- commit changes in Test CopyFromBeta
Query Generator: context query: link with specific community or claimed in community's dashboard
[Trunk | Claims Service]: EmailSender.java: Remove "beta" prefix from link for community dashboard when sending email notification for community claims.
Updates to Migrate community claims from Beta to Production
CommunityUtils: chnage methods from static, add it with autowired in EmailSender update properties
Update email Sender and Scheduler:
rename property emailScheduler.sendEmailNotifications to services.claims.mail.sendEmailNotifications
Add properties to enable/disable notifications for specific entities: services.claims.mail.notifyCommunityManagers services.claims.mail.notifyProjectManagers
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
View revisions
Also available in: Atom