coneda / kor Goto Github PK
View Code? Open in Web Editor NEWConedaKOR – store.manage.retrieve.
Home Page: https://coneda.net
License: GNU Affero General Public License v3.0
ConedaKOR – store.manage.retrieve.
Home Page: https://coneda.net
License: GNU Affero General Public License v3.0
a script to list the permissions of a given user on database objects (e.g. collections) would be useful
This could be done by modifying config.ru à la:
setup = Proc.new do |env|
[200, {'content-type' => 'text/html'}, ["setup"]]
end
wrapper = Proc.new do |env|
if File.exists?("#{RAILS_ROOT}/config/database.yml")
unless defined?(Kor::Application)
require "#{RAILS_ROOT}/config/environment"
end
Kor::Application.call(env)
else
setup.call(env)
end
end
run wrapper
They are converted only after editing and saving the entity again.
It seems that this is only happening when using the multi file upload. Currently, files are transmitted with a content type "aplication/octet-stream" which leads paperclip to believe that it shouldn't be doing any image-related processing.
cf. title
trying to access OAI-PMH interface with verb GetRecord triggers a 403 Forbidden response even though logged in
afaik the version 2.0 offers only the new way to link entities (btw: smart function but a little bit confusing under ui resp. usabilty aspects). anyway, why do we still need the section „session“?
I get the following errors when validating the ListRecords-XML doc for repo .../api/oai_pmh/kinds.xml against the aoipmh schema:
Element '{http://www.openarchives.org/OAI/2.0/}request', attribute 'verb': [facet 'enumeration'] The value 'ListRecord' is not an element of the set {'Identify', 'ListMetadataFormats', 'ListSets', 'GetRecord', 'ListIdentifiers', 'ListRecords'}.
Element '{http://www.openarchives.org/OAI/2.0/}request', attribute 'verb': 'ListRecord' is not a valid value of the atomic type '{http://www.openarchives.org/OAI/2.0/}verbType'.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
Element '{http://www.openarchives.org/OAI/2.0/oai_dc/}dc': No matching global element declaration available, but demanded by the strict wildcard.
kor subcommand reset-admin-account doesn't work
Errors result in an entry within the database that can later be inspected. This is generally good but the catching code has to throw more meaningful and consistent error messages.
Currently, nothing is shown when the user has no full name.
cf. title
... unless a specific entity type is selected.
Change: Allowing the user to select more than one target entity, when using the new relationship functionality. This could enhance the workflow, especially if the user is working on a particular batch of items, which all belong together. With "last created", he could easily create several relations at once.
Example: Selected entity "Leonardo da Vinci", selecting relation "has created" and then selecting works "Mona Lisa" and "Last supper".
Reasoning: research assistants often upload images in batches, and then continue on to add relations.
There is javascript in place that should change old /entities/1234
links to the newer /blaz#/entities/1234
version. However, it changes them to /blaze/1234
the records of response for OAI-PMH verb GetList request don't contain the record's collection id
it would be useful if OAI PMH's Identify request would not only return the repository's name or its URL but also a uuid for this repository
We are now trying to embed a KOR format within DC. This is very ugly so we will add a second metadata format in the OAI-PMH responses. The DC version will just contain very basic information (title, uuid, type, etc).
starting point: select expert search.
steps to reproduce: select an entity type -> additional fields for this selected type appear.
enhancement: as soon as a type is selected, display search results for that type. The same is already the case for the simple search. This would provide the user an immediate response to his selection, without going to the search button first. From there on the user can enter search terms and continue to narrow his search results.
This is now a mess of several config files being managed partly by ops directly and partly via the web interface. We should:
configs
table within the dbWhen a fully javascript based frontend is ready, we can even tie in the database configuration via a small dedicated rack app. This could give a php-style experience where you can set the database details often directly via the web interface.
starting point: The user is on a specific entity and is trying to add a new relationship with the new functionality in v2.0.
steps taken: The user selects a possible relationship from the dropdown menu and starts typing the target entity. Results are being shown.
problem: The results displayed don't take into account the possible target entity types. Although each relationship has clearly defined entity types on both ends.
... once we defined it.
Now, the workflow is to "mark" an entity, then navigate to another and then create the link between them. This should be done by an inline editor on the entity page.
Currently, kinds, relations and credentials have their description fields set to a string with length limited to 255 characters, this should be changed to 'text'.
starting point: The user is on a specific entity and is trying to add a new relationship with the new functionality in v2.0.
steps taken: The user selects a possible relationship from the dropdown menu, selects a target entity and adds the relation.
problem: The relation is accepted, even of the relationship type is not meant for the two entity types used.
example from the screenshot: person is being connected to a city with relation "wird dargestellt von".
currently information concerning relations can only be derived via instance data represented by relationships; it would be nice to be able to request relations directly, so that one could deal more easily with changes at the graph's schema level
starting point: open relationship editor on any given entity
steps to reproduce: click on "last created"
problem: currently 12 objects are shown, which causes unnecessary scrolling to create the new relationship. Would it make sense to reduce the objects to 9, meaning a 3x3 matrix? Or to allow the user to define the amount of objects or to allow the user to flip through several pages of these?
See /tools/statistics
starting point: The user is on a specific entity and is trying to add a new relationship with the new functionality in v2.0.
steps taken: The user selects a target entity from one of the three possible tabs (search, last visited, last created), before choosing a relationship type.
problem: Now the dropdown menu is still showing all relationships and is not dynamically reducing them to the ones possible for the two entities chosen.
reasoning: this addition would help databases with large amounts of relationship types, as the non relevant and not usable relationship types would not even be shown as an option.
as with entities it would be practical to get the relations uuid when requesting relationship records
currently information concerning kinds can only be derived via instance data represented by entities; it would be nice to be able to request kinds directly, so that one could deal more easily with changes at the schema level
The flash session middleware and the upload mime fix have to be reinstated.
New users have to accept a set of usage terms defined by the admin. Since we have the possibility of a guest account, that feature doesn't make sense (in that situation). Should we keep it? If yes: how should we handle the guest user?
A few improvements to the admin interface:
Spawning and detaching processes in ruby:
pid = Process.spawn('bin/delayed_job -n 2 run')
Process.detach pid
There should also be a public read-only action that allows querying the status of background jobs (pending/running or not)
in order to map the local from and to ids of relations, the local id of kinds is necessary. These are not exported via oaipmh's ListRecords
That also provides a solution for audio.
how shall they be differentiated when there are collections with the same name in different instances?
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.