jira-issues-migration issueshttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues2018-04-28T13:24:18Zhttps://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/1Add Segment type in Model that will enable to point to a particular SpatioTem...2018-04-28T13:24:18ZYann MombrunAdd Segment type in Model that will enable to point to a particular SpatioTemporal fragment of a Video MediaUnitLocalising an object on a particular frame of a Video in Model 1.1.x and 1.2 is time consumming.
You need first to define a TemporalSegment on your Video.
Create an Image MediaUnit to represent the extracted frame.
Then you can localise ...Localising an object on a particular frame of a Video in Model 1.1.x and 1.2 is time consumming.
You need first to define a TemporalSegment on your Video.
Create an Image MediaUnit to represent the extracted frame.
Then you can localise the object on this frame through a SpatialSegment.
If we define a new SpatioTemporalSegment that have both spatial and temporal components it will ease this process.WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/2Add Segment type in Model that will enable to track an Object in a MediaUnit2018-04-28T13:24:18ZYann MombrunAdd Segment type in Model that will enable to track an Object in a MediaUnitSometimes (especially in Video) you want to track an object that appears several times in the same MediaUnit.
It may be done through a TrackingSegment (name to be defined) that contains an ordered List of Segment.
Sometimes (especially in Video) you want to track an object that appears several times in the same MediaUnit.
It may be done through a TrackingSegment (name to be defined) that contains an ordered List of Segment.
WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/3Description of some classes of the Model are outdated2018-04-28T13:24:18ZYann MombrunDescription of some classes of the Model are outdatedEspecially LowLevelDescriptor and Segment.Especially LowLevelDescriptor and Segment.WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/4Move every test cases to JUnit 4 format2018-04-28T13:24:18ZYann MombrunMove every test cases to JUnit 4 formatSince we changed the dependency that is included by default it should be necessary to modify every test case to suit with JUnit 4 syntax.Since we changed the dependency that is included by default it should be necessary to modify every test case to suit with JUnit 4 syntax.ANNOTATOR-1.2.4https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/5Replace EADS by Cassidian in Copyrights in WebLab Core.2018-04-28T13:24:18ZYann MombrunReplace EADS by Cassidian in Copyrights in WebLab Core.Sometimes EADS or EADS Defence & Security is still defined defined as the right holder.Sometimes EADS or EADS Defence & Security is still defined defined as the right holder.ANNOTATOR-1.2.4https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/6Remove src/site from every project since this plugin is not used anymore.2018-04-28T13:24:18ZYann MombrunRemove src/site from every project since this plugin is not used anymore.WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/7Package fails due to plugins not maintained in Maven 3.x2018-04-28T13:24:19ZYann MombrunPackage fails due to plugins not maintained in Maven 3.xA lot of plugins, especially maven site are not fully compliant with Maven 3.
When we try to package some project it fails due to these plugins.
A lot of plugins, especially maven site are not fully compliant with Maven 3.
When we try to package some project it fails due to these plugins.
WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/8Improve the SegmentFactory2018-04-28T13:24:19ZYann MombrunImprove the SegmentFactoryCurrent SegmentFactory only helps for trhe creation of LinearSegment.
It should ease the creation of every types of Segments.Current SegmentFactory only helps for trhe creation of LinearSegment.
It should ease the creation of every types of Segments.WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/9Improve the WebLab ontologies to better fit the multimedia processing2018-04-28T13:24:19ZYann MombrunImprove the WebLab ontologies to better fit the multimedia processingWe need more properties to link MediaUnit together, expressing the type of transformation that enabled it (translation, transcription, synthesis, summarising, etc.).
On top of that, the chnages in the model (new segments) are impacting t...We need more properties to link MediaUnit together, expressing the type of transformation that enabled it (translation, transcription, synthesis, summarising, etc.).
On top of that, the chnages in the model (new segments) are impacting the structure ontology.WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/10WebLab.java is not consitent with model.owl / processing.owl / retrieval.owl2018-04-28T13:24:19ZYann MombrunWebLab.java is not consitent with model.owl / processing.owl / retrieval.owlAfter the chnages in theses ontologies, the Java class of the constants should be modified.After the chnages in theses ontologies, the Java class of the constants should be modified.WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/11Change accessor to some class variables and methods2018-04-28T13:24:19ZGérard DupontChange accessor to some class variables and methodsWhile trying to extend this portlet using the new WAR dependency mechanism, it appears that some element of the portlet class need to be acessed by the sub-class. Thus their accesor need to be changed from private to protected.While trying to extend this portlet using the new WAR dependency mechanism, it appears that some element of the portlet class need to be acessed by the sub-class. Thus their accesor need to be changed from private to protected.WebLab Core 1.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/12Migrate to model 1.2.12018-04-28T13:24:19ZYann MombrunMigrate to model 1.2.1Start migrating to the version 1.2.1.Start migrating to the version 1.2.1.WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/13Integration of query saving capabilities2018-04-28T13:24:19ZGérard DupontIntegration of query saving capabilitiesIn order to ease the integration of alert and collection projects definition from the search portlet, some evolution are needed. The goal is to enable to possibility to save a query through a simple button on the inerface. This will gene...In order to ease the integration of alert and collection projects definition from the search portlet, some evolution are needed. The goal is to enable to possibility to save a query through a simple button on the inerface. This will generate an event that could be catch by external portlet for different purposes.
Update have been tested (as well as some refactoring to ease reuse of the porlet) and everything is configurable trhoguht the standard spring configuration XML (by default theres is no change).
Attached is the patch proposed.https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/14Update WebLab Ontologies2018-04-28T13:24:19ZArnaud SavalUpdate WebLab OntologiesWebLab ontologies must be updated:
* model.owl
* processing.owl
* retrieval.owl
They contain incoherent properties or unused elements that do not relate to their intended use.
We also need to add some properties for futures features (t...WebLab ontologies must be updated:
* model.owl
* processing.owl
* retrieval.owl
They contain incoherent properties or unused elements that do not relate to their intended use.
We also need to add some properties for futures features (translation, transcription, synthesis, summarising ...)WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/15Define a portlet events specification with respect to all portlets2018-04-28T13:24:19ZArnaud SavalDefine a portlet events specification with respect to all portletsWeblab portlets are using portlets events to exchange WebLab Resources and other information.
However those events definitions and exchanged resources are not specified anywhere nor documented.
The first task might be to agree on a doc...Weblab portlets are using portlets events to exchange WebLab Resources and other information.
However those events definitions and exchanged resources are not specified anywhere nor documented.
The first task might be to agree on a documentation of published and supported events for each portlet.
The document defining inter-portlet eventing:
https://docs.google.com/document/d/1lO-1Gu2TpkNrSn38p2Lu_UvAgmFp02kfEwbkyDSa7is/edit?pli=1https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/16Old Junit 3.8.2 in portlet parent2018-04-28T13:24:19ZGérard DupontOld Junit 3.8.2 in portlet parentPom parent for Portlet is still importing the old Junit 3.8.2 whereas service parent is already in version 4.8.1. IT should be update (transparent update but easier tests with Junit4).Pom parent for Portlet is still importing the old Junit 3.8.2 whereas service parent is already in version 4.8.1. IT should be update (transparent update but easier tests with Junit4).WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/17Configure the folder crawler service to automatically deployable2018-04-28T13:24:19ZArnaud SavalConfigure the folder crawler service to automatically deployableThe current 1.5.1 version is not automatically deployable, it should.The current 1.5.1 version is not automatically deployable, it should.WebLab Core 1.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/18Generate XML resources in tests2018-04-28T13:24:19ZArnaud SavalGenerate XML resources in testsWhen an update of the WebLab Model is defined, old WebLab serialized resources in unitary tests becomes unusable.
Thus most of unitary tests must be rewritten.
To avoid this refactoring, xml files with serialized WebLab resources should...When an update of the WebLab Model is defined, old WebLab serialized resources in unitary tests becomes unusable.
Thus most of unitary tests must be rewritten.
To avoid this refactoring, xml files with serialized WebLab resources should be removed from test resources.
WebLab tests resources should be generated from an initialization method before running unitary tests.WebLab Core 1.2.5https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/19Improve the SegmentComparator2018-04-28T13:24:19ZYann MombrunImprove the SegmentComparatorNew Segment have been created. This implies that the Comparator has to be updated to handle SpatioTemporalSegment and TrackSegment.New Segment have been created. This implies that the Comparator has to be updated to handle SpatioTemporalSegment and TrackSegment.WebLab Core 1.2.2https://gitlab.ow2.org/weblab/various/jira-issues-migration/-/issues/20Improve the SegmentUtil2018-04-28T13:24:19ZYann MombrunImprove the SegmentUtilSegmentUtil contains method to test inclusion of Segment inside one other.
This has to be updated to handle new type of Segment (SpatioTemporal and Track).SegmentUtil contains method to test inclusion of Segment inside one other.
This has to be updated to handle new type of Segment (SpatioTemporal and Track).