LATC 24-7-platform issues

LATC / 24-7-platform

24/7 Interlinking Platform

http://latc-project.eu

15 stars 4 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

QA integration

#39 mhausenblas opened 11 years ago
0
DSI integration

#38 mhausenblas opened 11 years ago
2
Multiple root elements found

#37 cgueret opened 11 years ago
0
No property path

#36 cgueret opened 11 years ago
0
Learning does not work

#35 cgueret opened 11 years ago
0
Problem using VoID file

#34 cgueret opened 11 years ago
0
The Console should bootstrap a record in the MDS for every new link spec it receives

#33 cgueret closed 12 years ago
1
Fix external library usage in the Console

#32 cgueret closed 12 years ago
1
Console pom.xml

#31 cgueret closed 12 years ago
2
MDS <--> Runtime

#30 nurainir closed 12 years ago
2
sparql endpoint exception handling

#29 nurainir closed 11 years ago
0
Implement vetting process in the Console

#28 cgueret closed 12 years ago
1
Implement API to duplicate linkspec across workspaces in the Workbench

#27 cgueret closed 12 years ago
0
Metadata on generated linksets in the MDS

#26 cgueret closed 11 years ago
1
QA component is integrated in the Runtime

#25 cgueret closed 12 years ago
1
Vetting

#24 cgueret closed 12 years ago
0
public Console that reports on overall system status (@@ what goes in there?)

#23 cgueret opened 12 years ago
1
There is decent end-user documentation for the entire process

#22 cgueret opened 12 years ago
0
Generated linksets are available for download

#21 cgueret closed 11 years ago
0
The Runtime runs on the Sindice main cluster, not testhbase, and produces results that are pushed to the MDS

#20 cgueret opened 12 years ago
0
There is good error reporting from the Runtime on that web page and in RSS feed

#19 cgueret opened 12 years ago
0
There is an RSS feed where one can subscribe to the results for any given link spec

#18 cgueret closed 12 years ago
1
There is a nice web page where one can see the results for any given link spec

#17 cgueret opened 12 years ago
1
Runtime doesn't get stuck on SPARQL queries that take too long or other snafus

#16 cgueret closed 12 years ago
1
Runtime runs automatically without operator intervention

#15 cgueret closed 12 years ago
1
Edited specs are automatically scheduled for re-execution in the Runtime

#14 cgueret closed 12 years ago
1
One can somehow select host-based datasets as data sources in the Workbench (@@ how?)

#13 cgueret opened 12 years ago
0
One can use the dataset URIs from the DSI in the Workbench

#12 cgueret closed 12 years ago
0
Sindice endpoint allows host-based queries without timing out or rejecting queries

#11 cgueret opened 12 years ago
0
DSI allows access to basic Sindice stats (so one can check if a given domain is covered by Sindice)

#10 cgueret opened 12 years ago
2
DSI allows browsing and searching for curated datasets to find their URIs

#9 cgueret opened 12 years ago
0
When logged in, one can create a linkspec in the Workbench and preview generated links

#8 cgueret closed 12 years ago
1
With an account, one can access the Workbench and get a personal workspace there

#7 cgueret closed 12 years ago
0
There is some location where one can sign up for an account and log in

#6 cgueret closed 12 years ago
1
Documented deployment procedure for all components

#5 cgueret opened 12 years ago
0
Sensible hosting arrangements for all components (on as few machines as possible)

#4 cgueret opened 12 years ago
1
Components (workbench, console) are consolidated under final and sensible domain names

#3 cgueret closed 12 years ago
1
Make the frontpage clickable

#2 cgueret closed 12 years ago
0
Prevent name duplication in the console

#1 cgueret closed 12 years ago
1