language-research-technology / crate-o Goto Github PK

To be provided by @benfoley, an exact phrase

Something like:

Not to be used for native title claims

An external reference is an object that only has @id, eg {"@id": "https://example.com/something"} and there is no entity with the same @id in the crate. If the @id is a valid URL, it should be made into a link that opens a new tab in the web browser. Otherwise, it should enter the create new entity mode.

• Text
• TextArea <-- NOT NEEDED
• Number
• Date, DateTime, Time
• Geo
• URL
• Select, SelectURL, SelectObject <-- SelectURL probably not needed just work with {"@id": "https://..."}
• Value <-- This is problematic -- do not implement until we have a use case

Let a use define extra metadata, such as contextual entities using a spreadsheet (ATM these replace anything in the existing RO-Crate).

Editing of JSON-LD context

• Remove geo shape schema.org support
• Fix Leaflet bug
• Test whether the conversion works properly: the LAT LONG order (unit testing)
• Points
• Boxes
• Remove all other kinds of input support (in the UI, no test)

Incude in <./components/EntityProperty.vue> but also useable when listing crate contents like in BrowseEntities.

hasDefinedTerm
inDefinedTermSet
mentions

Should be in the default input group

• Use rochtml as a library and implement it into crate-o
• Detect if a folder already has an ro-crate-preview.html made by another tool and dont overwrite it
• make a slider to switch on/off auto-saving preview.html

For example, we can use something like https://github.com/ldodds/schema-icons to generate a set of icons.

When making a "#" URI need to escape or remove non-URI characters (eg space)

Replace createWebHashHistory with createWebHistory in the router
This needs testing on github pages

Best way to support this might be to implement an internal default layout now:

• Instead of calculating an order in getEntityTypesDefinitions and returning a array, return an object keyed by the property ID
• Use a default layout to show an About "tab"
• Put everything else into "..."

Layouts could be implemented so the "tabs" are either vertical or horizontal and simply jump to a part of the long form we already have so you can still scroll up and down or as seperate pages.

Several issues:

Example:
the root dataset needs to have RepositoryCollection and should not allow to change the Dataset other ones can be changed

Also make sure conformsTo is in the About group in the interface

Get datapacks working for languages

For Citation and anything to do with CreativeWork

Maria to see what is actually viable: about an API and sources.

When clicked remove the entity from the current prop. If it's the last one WARN the user and let them keep it in the crate as an unlinked entity

• Maybe its layout support, we need to remove layout support
• Test that it works with base_profile and Alex's (as him to get it)

Things that display natively in browser:

• Images
• Audio
• Video
• Text
• PDF
• Office Formats

Not sure how to do this? Use a conforms-to URI somewhere? Maybe use an UpdateAction to record editing sessions?

We already have lookups, can they be hooked up with geo data?

ATM it is not possible to add an entity such as a CreateAction -- need a button that can create an Orphan entity from the available Classes.

Show some links to the things that link here -- click to edit.

Add a button to display JSON output.
Some ideas:

• Edit raw JSON with simple text editor
• Compare diff between before and after edit

The github pages link https://language-research-technology.github.io/crate-o should redirect to https://language-research-technology.github.io/crate-o/main for the latest stable production release.
Use the branch name to provide test/staging version, for example: https://language-research-technology.github.io/crate-o/feature-1

Background

if you want to record the provenance of a File that is done with a a CreateAction entity, where the result property links to the File. But as the result Property is not on the File then there is no way to enter this.

Similarly when displaying the File it would be good to show that it is linked to the CreateAction -- See the way Describo does this

What to implement

We need to implement the Describo "resolve" idea in some form, using the same profile syntax if possible, so that a user can (for example):

• Link a file to a new CreateAction as result (or a person to a new CreateAction as an Agent)
• See such links when viewing a File or a Person object

Explore LaMeta and see what we can use in Crate-O

Put all the top two groups together

Just slurp up files and add them, as per existing Describro implementation

Can be the same as when property values are listed.

Just list the entities in the Crate using the widget from #2

Also allow a checkbox to say "Show Unlinked entities"

For People.

When there is more than one relationship eg hasPart and mainEntity then two things show up in reverse links -- add the property so it is easier to see why and what the relationships are

The "Other" input group can be long and messy - would be better to (a) sort it and (b) paginate it and (c) make it searchable

Only do things that are allowed in the profile