- changed status to open
Subgroup community posts [Probeaufgabe]
E.g. for conference proceedings it would be nice to list all papers that appeared in the proceedings. Please add a option to subgroup community posts (~ this community post appeared in the other community post).
Comments (11)
-
reporter -
- Are you referring to community posts?
- Already BibTeX supports a solution for that: the
crossref
field. Of course, BibSonomy also supports that field. A first step would be to add links to posts which are using that field. - For the full functionality the
crossref
field likely is not sufficient, since- it is intended for BibTeX and therefore, is using the BibTeX key to reference other resources (we would need the inter hash, though)
- it is not indexed in the database, therefore getting all publications of a conference would be difficult
- A solution could be to add a separate
part of
column (including appropriate indexes) to the community posts table.
-
reporter to 1. yes, but when i integrated them, they were called gold standards :)
to 2. - 4. I think we should not use the crossref because of the reasons you mentioned. We could add a separate column to the community table because of the absence of data, but we could also use the table that currently stores the references and add there a column. Then the resulting table would store any relation between two community posts (a more general table). Of course, we should rename the table then.
-
reporter - changed title to Subgroup community posts
- edited description
-
Probeaufgabe
-
reporter - changed title to Subgroup community posts [Probeaufgabe]
-
Account Deleted -
assigned issue to
According to Stephan Lutful is working on this
-
assigned issue to
-
Account Deleted why only for community posts? I thought about an automatically calculated hashcode of the proceedings/journal string as a journal/proceedings entity-id for establishing the links. The hashcode could be calculated from the plain string after stopword-removal and applying common abbreviations in titles (see comment on #121). The link could also be stored in a separate table (content_id, journal_hash) if the db-update is too slow. For the purpose of displaying the sub-publication entries on the publication details page, searches are probably sufficiently efficient using joins as well.
-
reporter -
assigned issue to
-
assigned issue to
-
reporter - changed milestone to 3.7.0
- changed component to webapp-bootstrap
-
reporter - changed status to resolved
- Log in to comment