Demo & discussion
Questions/comments
Nimisha: Validation on organization entry? Drop down?
We have server-side validation, which is great for now.
Marco: Probably keep assets and source for debug-only.
Kyle: Or edx-staff-only
HTML, Video cannot be edited currently. Studio endpoints are 500ing.
Tasks exist for Studio PRs to fix some of these.
Former user (Deleted) - send Dave Ormsbee and Kyle McCormick info on these issues.
Library Listing
Nimisha: Anticipate need for searching, sorting, filtering, large number of libraries
Dave: Keep permissions in mind too with indexing
Communication on UX design, decisions
Emulate current experience, except header
Component editor
Header
Ticket with edX discussion: https://openedx.atlassian.net/browse/TNL-7403
Former user (Deleted) has rolled his own header.
Should it be considered temporary? Or are we going to go live with it?
Rollout
All at once? Iterative?
Marco: Would it be easier to roll out specific types of libraries? (video-only, problem-only, etc)
Adolfo:
Legacy libraries can be created as before, no backwards-compatibility breakage
Plan was to roll out Source from Library XBlock for blockstore libraries only
Nimisha: Keep migration separate from rollout.
Dave: We need not to lose sight of importance of removing old libraries before wrapping up project.
Review project status
In review:
43% of hours used.
How do we feel about the feasibility of meeting the goals of the project within the allocated hours?
Let’s find a better way to share the status of project roadmap.
Walking through Discovery doc:
Integration testing: Do not do now; edX may just handle making this framework.
Nimisha: Keep metrics in mind. Be able to tell how many people are using these new features. Will be its own action item, but flagging now.
Dave: Library types: Complex/Video/Library. Why have these different library types?
Complex was anticipated to be harder because of authoring UI, which would involve structure.
Are the different library types any different, or just a thin veneer?
The latter.
Studio author view is not suited for presentation in React for certain blocks.
Elasticsearch - We are going from version 1 to version 7.
Keep this in mind when adding indexing/searching code.
Optimizations for library search
Will likely take until September, and some future optimizations may come out of it.
This affects LabXChange as well.
Would be good to use metrics and then leveraging them via NewRelic, to become more informed about these optimizations.
Is Organization app installed in stage/prod?
Yes, but not in edge
We should probably use that by default
Question: Edge?
Staging environment
library-authoring.stage.edx.org exists as of this morning (8/20), but is showing 500s. Kyle McCormick will investigate these.
Meta
Feedback?
Issue tracking
Currently:
OpenCraft makes action items visible via Open Action Items and Status Updates on wiki page.
edX makes action items visible via “Relevant Jira Stories” macro on wiki page, which really just pulls in every ticket on the BD-14 epic.
Is that working for everyone?
Meeting cadence
Back to once-a-month? More? Less?
Short answer: More often. Meeting later this week.
$customHeader
Manage space
Manage content
Integrations