Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New widget - set .attributes of a feature or Table #6919

Closed
borondics opened this issue Oct 17, 2024 · 4 comments
Closed

New widget - set .attributes of a feature or Table #6919

borondics opened this issue Oct 17, 2024 · 4 comments
Assignees

Comments

@borondics
Copy link
Member

borondics commented Oct 17, 2024

What's your use case?

We are using attributes more and more to carry information about the dataset. However, it doesn't seem possible to add new attributes from inside Orange. This becomes a problem if the necessary fields are not populated for any reason.

What's your proposed solution?

It would be great to have an Add attribute widget, where the user would specify the name of the attribute and then the value (string).

Are there any alternative solutions?

One can edit files but in that case they would need to conform to the individual file structure.

@ajdapretnar
Copy link
Contributor

Like a mash-up between Formula and Create Table?

@borondics
Copy link
Member Author

Actually, it could be a feature addition to Formula but it would insert information into the Table or the Feature attributes...

@markotoplak markotoplak changed the title New widget - add attributes New widget - set .attributes of a feature or Table Dec 25, 2024
@markotoplak
Copy link
Member

markotoplak commented Dec 25, 2024

Setting .attributes of a Variable would go into Edit domain.

Setting .attributes of a Table (as shown in Data Info). No idea. We only used these internally for now (for example setting species in bioinformatics add-on). I am not sure exposing them makes much sense.

An alternative here is to use the Python script widget when needed.

I see this issue describing two wholly separate problems. And I am not really sure if these things should get exposed.

@markotoplak
Copy link
Member

Setting .attributes manually should never be necessary.

In Bioinformatics, they ere designed so that if a user selects a specific species in one widget, other widgets will use that as a default. So, .attributes were used as something optional and not functionally necessary.

If .attributes are required I think a custom widget for setting them is in order, like As fairness data from the Fairness add-on. In such cases, values should be carefully crafted so that they are valid (and they are not limited to strings anyway).

So I'd say this is a wontfix. If anyone needs them, there should be a custom setter widget.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants