Improved CSV import #230
Replies: 1 comment 3 replies
-
#232 has an example that would benefit from the functionality above. A good start would be to merge the Proceedings Title Parser and dlpconf tools to a single Scientific Event Corpus Tool (SEC?) . For a start it is sufficient that the dblp conf tool uses the event_all database of PTP and the PTP API. Later the search interface can be migrated. We'd love to have an API where each event series and event has it's own restful endpoint. To do so we need to be able to uniquely identify an event series or event. Since most series don't have PIDs yet this would be a good starting point to get PIDs for the once we are interested in. As long as we do not have PIDs we'll use Pseudo-PIDs that is the event identifiers of our source systems e.g. wikidata, dblp, wikcfp, GND, or if all fails the acronym. |
Beta Was this translation helpful? Give feedback.
-
To speed up entry or relevant data for event series and improved CSV "round trip" could be very valuable. This way spreadsheet-tools such as Excel might be used for quick data updates.
Take the series https://confident.dbis.rwth-aachen.de/or/index.php?title=FCT as an example. Manually editing all entries in a column takes some 50 minutes. With a CSV round trip this time could be reduced to a few minutes e.g. since formulas might be used and cut&paste of entries is much easier.
Beta Was this translation helpful? Give feedback.
All reactions