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

As an artist, I want to be able to test an artwork easily, so I can see it before including in an exhibition. #232

Closed
vjpixel opened this issue Jul 14, 2019 · 11 comments
Assignees
Labels
artist bug Something isn't working CMS enhancement New feature or request
Milestone

Comments

@vjpixel
Copy link
Member

vjpixel commented Jul 14, 2019

Right now, to an artist to test an artwork s/he needs to create an exhibition. If s/he wants to improve the content, s\he needs to delete the exhibition and the artwork, and then update (or create) a new object (or marker), and then create the artwork and exhibition again.

An artist needs to be able to test an artwork without creating an exhibition.

The way it is now, every artist is automatically a curator because it needs to test their own work, so the "Jandig Curator" count isn't accurate.

I propose to have URLs https://jandig.app/artwork/XXX where XXX is the name of the artwork.

@vjpixel vjpixel added the enhancement New feature or request label Oct 8, 2019
@vjpixel vjpixel added this to the Launch milestone Jan 4, 2020
@vjpixel vjpixel changed the title An artist needs to be able to test an artwork As an artist, I want to be able to test an artwork easily, so I can see it before including in an exhibition. Jan 26, 2020
@vjpixel vjpixel added the bug Something isn't working label Jan 26, 2020
@anacforcelli anacforcelli self-assigned this Jan 27, 2020
@vjpixel vjpixel added question and removed question labels Jan 27, 2020
@vjpixel vjpixel added XS and removed M labels Feb 10, 2020
@anacforcelli
Copy link
Contributor

Scope check:
-Test to see if it's actually implemented and working correctly

@vjpixel
Copy link
Member Author

vjpixel commented Feb 10, 2020

Please, describe how you solved the problem.

@anacforcelli
Copy link
Contributor

Firstly, I made a .../artwork URL, then a view to pass the context to this page. In the view, it gets the artwork's ID from the request, then uses the filter ( Object.objects.filter(id=X) ) method to return the artwork with said ID to the context that will be sent to the exhibit page (the exhibit.jinja2 file), thus making an AR scene with only one marker and one object the same way it's done in the actual exhibit page.

Thereafter, I added a preview button on the "my artworks" section that leads the user to this artwork's page. The front-end was messed up, but the issue is ok

@vjpixel
Copy link
Member Author

vjpixel commented Feb 10, 2020

The button should also be on the individual artwork's page. "See on AR viewer."

@anacforcelli
Copy link
Contributor

on the "see all artworks"?

@vjpixel
Copy link
Member Author

vjpixel commented Feb 10, 2020

No, this one:

Screenshot from 2020-02-10 17-44-13

@anacforcelli
Copy link
Contributor

anacforcelli commented Feb 10, 2020

So that you can see the artwork before even including it in the database?

@vjpixel
Copy link
Member Author

vjpixel commented Feb 10, 2020

I was creating an issue right now about this.

When you edit an artwork, it should show "Edit Jandig Artwork", but right now it shows the creation page.

Consider that this is the edit page.

@vjpixel
Copy link
Member Author

vjpixel commented Feb 10, 2020

I created #307 to deal with what I described above.

@anacforcelli
Copy link
Contributor

All right. Should I redirect it to the creation page as #307 isn't finished?

@vjpixel
Copy link
Member Author

vjpixel commented Feb 10, 2020 via email

anacforcelli added a commit that referenced this issue Feb 19, 2020
vjpixel added a commit that referenced this issue Feb 19, 2020
@vjpixel vjpixel closed this as completed Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
artist bug Something isn't working CMS enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants