poorejc commented on issue #266:
URL: 
https://github.com/apache/incubator-flagon-useralejs/issues/266#issuecomment-1186053223

   @kevbrowndev @EandrewJones wow timing is impeccable--of course I'm two weeks 
late to the convo :)
   
   Some students I've been working with have been doing some work in pulling 
attributes from SVG docs embedded in pages and adding those attributes to 
custom logs. EX: clicking around on an interactive dashboard map on [apache 
superset](https://superset.apache.org/), can we extract data attributes 
embedded within svg docs. Here's what extracted attributes look like:
   
   
![image](https://user-images.githubusercontent.com/12189190/179329397-34b7a82f-e052-45ee-9a6f-bd01efc0462a.png)
   
   Methods are slightly more complicated than retrieving html attributes via 
.getAttribute() (have to parse xml first), so unsure that `.dataset` method 
will work uniformly (or at all for our use case), however, certainly the intent 
of the extracted data is the same.
   
   Would love to coordinate with you all on modifying the UserALE.js data 
schema to specifically accommodate attached properties embedded in docs. 
Currently, we're using custom logs with custom fields--standardized option 
would be better. Might be able to engineer together an elegant common solution 
that uses new UserALE.js params in `userale.options()` to invoke fuctions to 
extract attributes from different sorts of docs (html, xml). @kevbrowndev is 
this what you had in mind? If, we're on the same page there, then yes 
`packageLogs.js` is exactly the right place to embed those functions. Might 
also expose them through the API to assist custom log scripting....
   
   @kevbrowndev @EandrewJones can you share some examples here? I'll work with 
my students to do the same.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@flagon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to