Create Google sheet smart chip work request

[saumier]

Work order created: https://docs.google.com/document/d/16esBj2X5tm4gW7x6C1xNli8ngdzJvpEliQcoia8zYyE/edit?usp=sharinghttps://docs.google.com/document/d/16esBj2X5tm4gW7x6C1xNli8ngdzJvpEliQcoia8zYyE/edit?usp=sharing

[saumier]

Here is the original email with the idea:

Salut Frédéric,

The bi-weekly yesterday made me think about a prototype of an event spreadsheet that could use Artsdata K-numbers for places and performers, organizers, event types, etc. instead of having to enter them manually.

The idea is to have a minimal template that would use smart chips so the user could roll over cells to see the full details from Artsdata.

Here is a Google sheet but without the smart chip (not built yet). But if you roll over the Main Webpage URL cell you can get an idea of a smart chip. https://docs.google.com/spreadsheets/d/1MY-6ckSH34Olw3hwKrJDSg7kbYlGinmDr5aRP6cvp2o/edit?usp=sharing

This proptype would develop 2 smart chip features of Google sheets:

1. preview-links - to make a card appear when you roll over the K-number to display the name and details from Artsdata.
2. Lookup - to enable a person to type a name of a place or person/organization into the cell and have it reconciile with Artsdata by showing a card with a list of matches to select. This would add the K-number to the spreadsheet.

This is the user flow:

1. open any new Google sheet
2. Add the "Artsdata smart chip" as an extension to your user account from Google market place.
3. From the Artsdata extension menu in Google sheets, select "create new events tab" (this opens a new tab with the standard column headers already added)
4. Enter you event data (for example in the performer cell start by typing the name of the performer and then selecting a match from the list from the smart chip)
5. Review your work (roll over K-numbers to see the full details in the smart chip)
6. From the Artsdata extension menu in Google sheets, select "login to Artsata" to login using your GitHub account
7. Enter a name for the artifact.
8. Click the "push to Artsdata" button

The events would be uploaded via the Artsdata Databus and minted (or linked) to an existing entity in Artsdata. The Artsdata K-numbers would be automatically added back to the spreadsheet as read-only.

If you need to create a new place or person/organization you could follow similar steps in a different tab. Like "create new places tab".

This protoytpe could be discussed in our next bi-weekly and if you think it is worth making it into a Work Order then I could assign one of my team members to make the "Artsdata smart chip" extension and we could test it out. One advantage of this approach is that the spreadsheet has very little code and therefore very little to maintain.

Regards, Gregory

--- response

Salut Gregory,

Thanks for this interesting idea!

Do you see this tool in place of Dessa's proposed spreadsheet, as features integrating in it, or as two tools that we would roll out simultaneously?

The mock-up that Dessa designed was meant to help a venue manager upload their in-house spreadsheet and convert it into RDF with a basic column-to-column mapping. It was also thought out so it could be used in any systems that accept JSON-LD inputs, not just Artsdata.

What you propose seems more suited for someone who would be filling in the spreadsheet from scratch. It requires a little more tech savvy than the other spreadsheet, but it would provide for a much, much more convivial user experience. Another big 'pro' is the fact that the smart chips could be used in other Google Sheet applications as well.

There might be merit to protoping the two tools and running them both through user acceptance tests...

FYI - I already pitched the other project to Christian and he's interested in working on it. Should we invite him to our next bi-weekly meeting and discuss the pros and cons of developing both tools simultaneously vs doing just the one to begin with?

Encore une fois merci!

Frédéric

[saumier]

Work order to review https://docs.google.com/document/d/16esBj2X5tm4gW7x6C1xNli8ngdzJvpEliQcoia8zYyE/edit?usp=sharing

Bonjour Gregory, I heard you've been away supporting your mother in Mexico. I hope everything is ok on this front. Since you could not attend today's bi-weekly meeting and discuss the merits of developing two Google Sheet prototypes concurrently, I made the decision of moving ahead with both. Here's a work request for your proposed Google Sheet with smart chips: https://docs.google.com/document/d/16esBj2X5tm4gW7x6C1xNli8ngdzJvpEliQcoia8zYyE/edit?usp=sharing Please note that A10s committed to a tight timeline in order to deliver Dessa with an MVP that she could promote at her ArtsReach workshop, on June 25. Would this timeline be feasible for Culture Creates?

[saumier]

@tammy-culture @troughc Please review the work order that I assigned to Fred incase you see any issues I missed. I think Suhail and Dev can do most of this work. https://docs.google.com/document/d/16esBj2X5tm4gW7x6C1xNli8ngdzJvpEliQcoia8zYyE/edit

[tammy-culture]

@saumier I made some adjustments to the payment schedule. Looks good.

[fjjulien]

@saumier Here's a question and concern regarding the user flow:

What would the user be expected to do if their location, organizer or performer entity does not exist in Artsdata yet?

In your initial email, you wrote: "If you need to create a new place or person/organization you could follow similar steps in a different tab. Like "create new places tab"." However, this feature is not included in the quote.

I'm not convinced it would be a good idea to invite users to create 'permanent' entities (as opposed to ephemeral events) into a Google Sheet.

• Data providers tend to be careless when populating any form. They might be even more careless if asked to do it in a Google Sheet (rather than a more formal looking user interface).
• In a user interface, we have a access to a range of tools to gently guide the user towards the expected behaviour: field label, field instruction, placeholder text, tooltips, etc. In a Google Sheet, we would have just a column label.
• Creating person and organization records that can be clearly disambiguated requires more than typing a name and an address. It also requires other kinds of information that may seem overkill and that a user may not be willing to provide (business number, legal name, person occupation, person work location).

If the goal of this tool is to generate data that Artsdata data consumers can reuse, it might be best not to ask users to create their own organization and person records. Places, perhaps. But for organizations and persons, I would bring in people like Dessa and Dorian to assist with the creation of records.

[saumier]

What would the user be expected to do if their location, organizer or performer entity does not exist in Artsdata yet?

@fjjulien For this project I agree to leave out the creation of new orgs and people. For the beta we ask people to only choose from existing places, people, orgs. Since place is mandatory, this will work well for events in a single venue and presenters that always perform in the same set of venues. In the roll-out phase, I can imagine feedback from users that may have multiple locations that need to be added. If needed we could add 6 place/address properties so that nested places with blank nodes are possible.

[fjjulien]

@saumier As discussed at the bi-weekly meeting, please consider a workflow for loading the JSON-LD from the MVP developed by A10s.