Ticket #981 (closed Enhancement: fixed)

Opened 8 years ago

Last modified 8 years ago

facetService.getFacet() to return a RelatedTopic instead of a simple Topic

Reported by: Malte Owned by: jri
Priority: Major Milestone: Release 4.8.3
Component: DeepaMehta Standard Distribution Version: 4.8
Keywords: Cc:
Complexity: 2 Area: Application Framework / API
Module: deepamehta-facets


This would simplify manual workspace assignments as the relating assoc would not need to be re-fetched otherwise to be assigned.

Having the facetService enhanced this way one could assign the potentially newly created Association simply do two things via one "getFacet()"

  • manually assign the facet topic value to a workspace
  • and additionally assign the relating assoc after easy access via facetTopicValue.getRelatingAssociation()

Are there any issues which would make this difficult or would this have any side-effects? If not, it would be great to go for it, i think.

Thanks for your support1

Change History

comment:1 Changed 8 years ago by jri

  • Status changed from new to accepted
  • Complexity changed from 3 to 2
  • Milestone changed from Release 4.8.1 to Release 4.8.3

comment:2 Changed 8 years ago by Jörg Richter <jri@…>

In 8136945db7802494a0f56be67c6a6b84f264ffd0/deepamehta:

Facets API: getFacet() returns RelatedTopic? (#981).

Facets API

2 changed methods:

RelatedTopic getFacet(long topicId,            String facetTypeUri);
RelatedTopic getFacet(DeepaMehtaObject object, String facetTypeUri);

A RelatedTopic is returned (instead a Topic).

Thanks to Malte for addressing this issue!

See #981.

comment:3 Changed 8 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.