Ticket #3 (closed enhancement: fixed)

Opened 3 years ago

Last modified 2 years ago

Map the feature column of a peak list to features in a platform

Reported by: business@… Owned by: m.s.vanvliet@…
Priority: minor Milestone:
Component: File Interpretation Version:
Keywords: Cc:

Description


Change History

Changed 3 years ago by m.s.vanvliet@…

  • owner set to m.s.vanvliet@…
  • status changed from new to assigned

Changed 3 years ago by m.s.vanvliet@…

  • status changed from assigned to accepted

Changed 3 years ago by business@…

  • component changed from Feature linking to Data Interpretation

Changed 3 years ago by business@…

  • type changed from user story to enhancement

When feature list is chosen as file type, the user should choose the target platform (also giving the possibility to create a new one) and be able to add a comment describing this version of the platform.
The feature list automatically gets a new version number for that platform.

Current uploaded peak files that are already assigned to an earlier version of the platform should not be updated automatically, as this may change the mapping (and most probably the peak list was indeed created using the older platform version).

For now, just the user that uploaded the peak list should be able to modify it. Uploading a new version of a platform is open to everyone for now.

Changed 3 years ago by work@…

Default colors used by the uploadr plugin are now as follows:

// colorpickr colors
colorPickerColors : [

'#bce08a', // default green
'#00a8e1', // blue
'#ff6418', // orange
'#c78cda', // purple
'#ffcb00', // yellow
'#e70033' // red

],

I guess it would be best to stick to these colors. I suggest the newly uploaded file to be a lighter shade of green, for example: #ddeec1

Also, to give a file a color when building up the uploadr field, you can do that by adding a 'color' argument to a 'file', e.g.:

<% path.listFiles().each { file -> %>

<uploadr:file name="${file.name}">

<uploadr:fileSize>${file.size()}</uploadr:fileSize>
<uploadr:fileModified>${file.lastModified()}</uploadr:fileModified>
<uploadr:fileId>myId-${RandomStringUtils?.random(32, true, true)}</uploadr:fileId>
<uploadr:color>#c78cda</uploadr:color>
<uploadr:deletable>false</uploadr:deletable>
<uploadr:ratingText>This is the tooltip text of the rating for ${file.name}</uploadr:ratingText>

</uploadr:file>

<% } %>

Also, when a new file has been uploaded, it will get the default green color. To override this behaviour you can use the 'onSuccess' event handler as follows:

<uploadr:onSuccess>

console.log('done uploading \ + file.fileName + '\);

// do some stuff
....

// override the background to light green
$('.progress',domObj).css('background-color', '#ddeec1');
console.log('and overrided the background color to #ddeec1');

// and set the rating tooltip text for the rating
file.fileRatingText = 'you just uploaded this file and in the onSuccess handler the rating tooltip text is added';

// callback when doen
callback();

</uploadr:onSuccess>

Note that the color for newly uploaded files should also be set when setting up the file uploadr... (see the uploadr:file above)

Changed 3 years ago by work@…

also see <uploadr:demo/> for more details / information / demo's....

Changed 3 years ago by work@…

sorry... these comments were for ticket #15...

Changed 3 years ago by business@…

  • priority changed from major to minor

Changed 3 years ago by s.h.sikkema@…

Current status:

- on assay page, there can be seen which data columns are mapped to which features
- rest controller for now still works with data column headers (getMeasurements returns them and getMeasurementData uses them)
- UploadedFileService?.getDataColumnHeaders returns headers from data
- UploadedFileService?.getFeatureNames returns overlap between headers and features

Changed 2 years ago by business@…

  • status changed from accepted to closed
  • resolution set to fixed

Works beautifully

Note: See TracTickets for help on using tickets.